CVE-2026-91006

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th 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
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.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.

Apache Karaf's instance-management service (InstanceServiceImpl) builds the command line used to launch a child Karaf JVM by string concatenation, then executes it through /bin/sh (Unix) or cscript (Windows). The caller-supplied javaOpts value is spliced into that string unquoted. A javaOpts value containing shell metacharacters (;, |, `, $(...)) is interpreted by the shell instead of being passed to the JVM as an option, giving arbitrary OS command execution as the Karaf process user.

Reachable via the shell commands instance:create, instance:start, instance:restart, instance:change-opts, and the equivalent InstanceMBean JMX operations (createInstance, startInstance, changeJavaOpts, cloneInstance).

Mitigation  * Set karaf.secured.command.compulsory.roles=admin in etc/system.properties to close the fail-open gap for all unconfigured command scopes. * Restrict which principals can reach instance:* commands and InstancesMBean via etc/users.properties role assignments. * Treat javaOpts passed to instance:create/instance:start/instance:change-opts/InstancesMBean as untrusted input only from fully-trusted operators.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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 28, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Sep 29, 2026
No patch confirmed yet.
generic

Pony Mail

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

Vendor Advisories for CVE-2026-91006(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 36× in last 7d / 36× 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 00:58 UTCEG score recompute
  2. 2026-10-04 00:58 UTCGHSA enrichment
  3. 2026-10-03 12:44 UTCGHSA enrichment
  4. 2026-10-03 00:30 UTCEG score recompute
  5. 2026-10-03 00:30 UTCGHSA enrichment
  6. 2026-10-02 12:16 UTCGHSA enrichment
  7. 2026-10-02 00:02 UTCEG score recompute
  8. 2026-10-02 00:02 UTCGHSA enrichment
  9. 2026-10-01 19:51 UTCEPSS rescore
  10. 2026-10-01 11:09 UTCGHSA enrichment
  11. 2026-09-30 22:56 UTCEG score recompute
  12. 2026-09-30 22:56 UTCGHSA enrichment
  13. 2026-09-30 15:04 UTCEPSS rescore
  14. 2026-09-30 10:42 UTCGHSA enrichment
  15. 2026-09-29 22:28 UTCGHSA enrichment
  16. 2026-09-29 21:26 UTCEG score recompute▲ 8.80
  17. 2026-09-29 21:25 UTCGHSA enrichment
  18. 2026-09-29 21:23 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  19. 2026-09-29 16:43 UTCGHSA enrichment
  20. 2026-09-29 16:24 UTCNVD update
  21. 2026-09-29 15:53 UTCEG score recompute
  22. 2026-09-29 15:53 UTCGHSA enrichment
  23. 2026-09-29 15:53 UTCMITRE cvelistV5
  24. 2026-09-29 14:57 UTCGHSA enrichment
  25. 2026-09-29 04:31 UTCGHSA enrichment
Show 11 more
  1. 2026-09-29 04:30 UTCNVD update
  2. 2026-09-29 04:00 UTCEG score recompute
  3. 2026-09-29 04:00 UTCGHSA enrichment
  4. 2026-09-29 04:00 UTCMITRE cvelistV5
  5. 2026-09-28 14:25 UTCGHSA enrichment
  6. 2026-09-28 14:23 UTCNVD update
  7. 2026-09-28 13:27 UTCGHSA enrichment
  8. 2026-09-28 13:27 UTCMITRE cvelistV5
  9. 2026-09-28 11:29 UTCNVD update
  10. 2026-09-28 10:52 UTCEG score recompute
  11. 2026-09-28 10:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91006?
CVE-2026-91006 is a high vulnerability published on September 28, 2026. Apache Karaf's instance-management service (InstanceServiceImpl) builds the command line used to launch a child Karaf JVM by string concatenation, then executes it through /bin/sh (Unix) or cscript (Windows). The caller-supplied javaOpts value is spliced into that string unquoted. A javaOpts value…
When was CVE-2026-91006 disclosed?
CVE-2026-91006 was first published on September 28, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91006 actively exploited?
CVE-2026-91006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91006?
CVE-2026-91006 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-91006?
No fix for CVE-2026-91006 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-91006 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91006?

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

Book a Demo →Browse All CVEs