CVE
C-Kermit auth bypass allows command execution via REMOTE QUERY
Affects C-Kermit 6.0.192 up to 11.0.514 running a server with host commands disabled and REMOTE QUERY or REMOTE ASSIGN enabled. Fixed in 11.1.515.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 11.1.515
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 11.1.515.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
C-Kermit, from OpenKermit, is affected by a remote code execution flaw that lets an attacker run shell commands on a server even when host commands are disabled. Attackers can reach it over the network without logging in, by sending crafted REMOTE QUERY or REMOTE ASSIGN and EXECUTE requests to a Kermit client.
Read the original description
C-Kermit 6.0.192 before 11.1.515 contains a remote code execution vulnerability that allows Kermit clients to run shell commands on servers with host commands disabled by abusing REMOTE QUERY evaluation. Attackers can send a REMOTE QUERY invoking the command function, or define a macro via REMOTE ASSIGN and call execute to reach RUN, bypassing the nopush restriction and DISABLE HOST.
Who should check
Teams running C-Kermit 6.0.192 through 11.0.514 as a server with host commands disabled (DISABLE HOST), where REMOTE QUERY or REMOTE ASSIGN is enabled.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 11.1.515.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129125 (C-Kermit 6.0.192 before 11.1.515 Command Execution via REMOTE QUERY), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129125 (entry last updated 2026-11-13):
Affected:
- OpenKermit C-Kermit: from 6.0.192, fixed in 11.1.515
Fixed versions: 11.1.515.
Conditions (all must be true for the bug to be hit):
- Affects C-Kermit 6.0.192 up to 11.0.514 (fixed in 11.1.515) (source: https://www.vulncheck.com/advisories/c-kermit-6.0.192-before-11.1.515-command-execution-via-remote-query)
- Server running with host commands disabled (DISABLE HOST) (source: https://github.com/OpenKermit/ckermit/security/advisories/GHSA-c5px-7h4c-gj8p)
- REMOTE QUERY and REMOTE ASSIGN are enabled (source: https://github.com/OpenKermit/ckermit/commit/85ef1da670cee132ea2d8e4eb759bab310ff73c9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129125 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129125 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OpenKermit/ckermit/security/advisories/GHSA-c5px-7h4c-gj8p
- https://github.com/OpenKermit/ckermit/commit/85ef1da670cee132ea2d8e4eb759bab310ff73c9
- https://github.com/OpenKermit/ckermit/releases/tag/v11.1.515
- https://github.com/OpenKermit/ckermit/blob/v11.0.514/ckcpro.w#L2544
- https://www.vulncheck.com/advisories/c-kermit-6.0.192-before-11.1.515-command-execution-via-remote-query
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129125
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129125"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- OpenKermit C-Kermit
From 6.0.192 · fixed in 11.1.515
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129125
Is CVE-2026-129125 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A Kermit client can run shell commands on the server even when host commands are disabled with DISABLE HOST. The bug is in the REMOTE QUERY and REMOTE ASSIGN handling, which allows commands to run this way.Source: vulncheck.com, github.com, github.com
Which versions are affected by CVE-2026-129125?
C-Kermit: from 6.0.192 before 11.1.515.Source: cve.now feed data
Am I affected, and how do I check?
C-Kermit versions from 6.0.192 up to 11.0.514 are affected, and 11.1.515 is the first fixed version. The setup that matters is a server that runs DISABLE HOST followed by SERVER, with REMOTE QUERY and REMOTE ASSIGN enabled, which are on by default. To check, compare the installed C-Kermit version against the range and look at the server's DISABLE HOST and QUERY/ASSIGN settings.Source: vulncheck.com, github.com, github.com
How do I fix CVE-2026-129125?
Upgrade C-Kermit to 11.1.515 or later. The facts name no patch IDs or workaround.Source: vulncheck.com, github.com, github.com