CVE-2026-91012

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (37th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

org.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties), which backs the "config" MBean and the config:* shell commands, derives the file it writes a configuration to from caller-supplied input without checking that the result stays inside ${karaf.etc}:

* if the submitted property map contains a felix.fileinstall.filename entry, that value is turned directly into a File (getCfgFileFromProperty), so it can point to any absolute path the Karaf process can write to; * otherwise the configuration PID is concatenated verbatim into the target file name (generateConfigFilename(): new File(karaf.etc, pid + ".cfg")), so a PID containing ".." segments resolves outside ${karaf.etc}. createFactoryConfiguration() has the same issue via the factory PID/alias.

Both code paths are reachable by any caller holding the "manager" role under Karaf's shipped command/JMX ACL (org.apache.karaf.command.acl.conf.cfg: "update = manager"). Such a user can therefore write attacker-controlled content to any file the Karaf process can write, including files the same ACL otherwise reserves to "admin" (etc/users.properties, etc/*.acl.*.cfg, etc/org.apache.karaf.management.cfg, and similar), allowing a manager-role user to grant themselves the admin role or otherwise take over the container.

ConfigMBeanImpl.install() and the config:install shell command already guarded the equivalent risk on their own code path with a finalname.contains("..") string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to ConfigRepositoryImpl.update() / createFactoryConfiguration() at all.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

October 1, 2026

Advisory Details (2)

Auto-updated Oct 1, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-91012: Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation

http://www.openwall.com/lists/oss-security/2026/09/28/8
generic

Pony Mail

https://lists.apache.org/thread/op8trtz1qxkdwj2rjozhd9yt2yd6nhw4

Vendor Advisories for CVE-2026-91012(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 11:36 UTCGHSA enrichment
  2. 2026-10-04 07:20 UTCGHSA enrichment
  3. 2026-10-04 03:05 UTCGHSA enrichment
  4. 2026-10-03 22:51 UTCGHSA enrichment
  5. 2026-10-03 18:36 UTCEG score recompute
  6. 2026-10-03 18:36 UTCGHSA enrichment
  7. 2026-10-03 14:19 UTCGHSA enrichment
  8. 2026-10-03 10:04 UTCGHSA enrichment
  9. 2026-10-03 05:49 UTCGHSA enrichment
  10. 2026-10-03 01:34 UTCGHSA enrichment
  11. 2026-10-02 21:19 UTCEG score recompute
  12. 2026-10-02 21:19 UTCGHSA enrichment
  13. 2026-10-02 17:03 UTCGHSA enrichment
  14. 2026-10-02 12:49 UTCGHSA enrichment
  15. 2026-10-02 08:34 UTCGHSA enrichment
  16. 2026-10-02 04:19 UTCGHSA enrichment
  17. 2026-10-02 00:02 UTCEG score recompute
  18. 2026-10-02 00:02 UTCGHSA enrichment
  19. 2026-10-01 19:51 UTCEPSS rescore
  20. 2026-10-01 19:38 UTCGHSA enrichment
  21. 2026-10-01 15:23 UTCGHSA enrichment
  22. 2026-10-01 14:21 UTCEG score recompute▲ 9.80
  23. 2026-10-01 14:21 UTCGHSA enrichment
  24. 2026-10-01 14:20 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  25. 2026-09-30 15:04 UTCEPSS rescore
Show 5 more
  1. 2026-09-29 14:57 UTCGHSA enrichment
  2. 2026-09-29 10:42 UTCGHSA enrichment
  3. 2026-09-29 09:25 UTCNVD update
  4. 2026-09-29 08:44 UTCEG score recompute
  5. 2026-09-29 08:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91012?
CVE-2026-91012 is a critical vulnerability published on September 29, 2026. org.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties), which backs the "config" MBean and the config:* shell commands, derives the file it writes a configuration to from caller-supplied input without checking that the result stays inside ${karaf.etc}: if the submitted…
When was CVE-2026-91012 disclosed?
CVE-2026-91012 was first published on September 29, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91012 actively exploited?
CVE-2026-91012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91012?
CVE-2026-91012 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-91012?
No fix for CVE-2026-91012 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-91012 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91012

Explore →

Is Your Infrastructure Affected by CVE-2026-91012?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs