CVE
Webmin through 2.670 Users File Injection via acl/cert_issue.cgi
Webmin 2.670 and earlier are affected, where an authenticated Webmin user can add a second root entry and gain Webmin root access after miniserv restarts. No fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Webmin 2.670 and earlier are affected Attacker must be an authenticated Webmin user Root access is gained after the miniserv service restarts
- 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? →
- 16/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? →
- Specific setups only
- 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
Webmin, a web-based system administration tool, is affected. An attacker who already has a low-privilege Webmin login can reach it remotely over the network and abuse the certificate issuing page to inject a second root account with a known password hash, gaining full Webmin root access once the service restarts.
Read the original description
Webmin through 2.670 contains a users file injection vulnerability in acl/cert_issue.cgi that allows authenticated Webmin users to inject lines by supplying unvalidated certificate DN fields containing newlines. Attackers can end a DN field with a backslash and newline to add a second root entry with a known password hash, gaining Webmin root access after miniserv restarts.
Who should check
Teams running Webmin 2.670 or earlier, where authenticated Webmin users can issue certificates through acl/cert_issue.cgi
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Webmin 2.670 and earlier are affected Attacker must be an authenticated Webmin user Root access is gained after the miniserv service restartsApply the patch listed under Evidence.
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-126781 (Webmin through 2.670 Users File Injection via acl/cert_issue.cgi), 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-126781 (entry last updated 2026-11-11):
Affected:
- webmin webmin: through 2.670
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Webmin 2.670 and earlier are affected (source: https://www.vulncheck.com/advisories/webmin-through-2.670-users-file-injection-via-acl-cert-issue-cgi)
- Attacker must be an authenticated Webmin user (source: https://www.vulncheck.com/advisories/webmin-through-2.670-users-file-injection-via-acl-cert-issue-cgi)
- Root access is gained after the miniserv service restarts (source: https://www.vulncheck.com/advisories/webmin-through-2.670-users-file-injection-via-acl-cert-issue-cgi)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126781 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126781 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/webmin/webmin/commit/0c449e341746d8c445c8c7db223eac1f41755943
- https://github.com/webmin/webmin/commit/8fb194e5fbc30a6664545d48940d03759ace9bf2
- https://github.com/webmin/webmin/blob/2.670/acl/cert_issue.cgi#L22-L52
- https://www.vulncheck.com/advisories/webmin-through-2.670-users-file-injection-via-acl-cert-issue-cgi
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-126781
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-126781"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- webmin webmin
through 2.670
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126781
Is CVE-2026-126781 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?
The flaw lets an authenticated Webmin user inject lines into the users file through acl/cert_issue.cgi. The injected line can add a second root entry with a known password hash, which gives Webmin root access once the miniserv service restarts.Source: vulncheck.com
Which versions are affected by CVE-2026-126781?
webmin: through 2.670.Source: cve.now feed data
Am I affected, and how do I check?
Webmin through version 2.670 is listed as affected, with 2.670 as the last affected version. Compare your installed Webmin version against that range, since the checked facts identify no other setup condition beyond holding an authenticated Webmin account.Source: vulncheck.com
How do I fix CVE-2026-126781?
The checked facts name no fixed version, so no upgrade target can be given from them. Check the Webmin project's advisory or release notes for a patched release and upgrade to it once it is published.Source: vulncheck.com