CVE-2026-82916

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-11-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-117474 (ENISA EUVD) · GHSA-63p5-rjv9-w7w3 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Missing Authorization in XmlDsDump in Apache OFBiz 24.09 before 24.09.08 on all platforms allows a remote authenticated attacker holding only the webtools base permissions (OFBTOOLS_VIEW, WEBTOOLS_VIEW) — explicitly not the ENTITY_MAINT permission the export feature declares and visibly refuses to render for — to export the contents of any database entity, including UserLogin with its currentPassword hashes, to any filesystem path the OFBiz process can write, including a web-served docroot, and to create arbitrary directories or truncate arbitrary existing files at those paths, because the XmlDsDump screen action writes the requested entity data via new FileOutputStream on unvalidated outpath and filename request parameters before the screen's ENTITY_MAINT permission check runs, unlike the equivalent Java service entityExportAll, which enforces both a permission check and a file-path allow-list. Users are recommended to upgrade to version 24.09.08, which fixes this issue.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 5, 2026

Last Modified

November 10, 2026

Advisory Details (1)

Auto-updated Nov 10, 2026
Fix named in the CVE record.
Web page

Pony Mail

https://lists.apache.org/thread.html/7b2syzksp7klt9fvhdg0olldvs2g83lz

Vendor Advisories for CVE-2026-82916(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-11-10 21:48 UTCEchelonGraph re-scored
  4. 2026-11-10 21:47 UTCGHSA enrichmentGHSA-63p5-rjv9-w7w3 · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-11-05 16:27 UTCGHSA enrichmentGHSA-63p5-rjv9-w7w3
  11. 2026-11-05 15:54 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  12. 2026-11-05 15:54 UTCGHSA enrichmentGHSA-63p5-rjv9-w7w3
  13. 2026-11-05 15:53 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  14. 2026-11-05 15:04 UTCENISA EUVD ID recordedEUVD-2026-117474 · Source: ENISA EUVD
  15. 2026-11-05 14:26 UTCNVD update
  16. 2026-11-05 14:09 UTCEchelonGraph re-scored
  17. 2026-11-05 14:08 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82916?
CVE-2026-82916 is a high-severity vulnerability; its CVE record was published on November 5, 2026. Missing Authorization in XmlDsDump in Apache OFBiz 24.09 before 24.09.08 on all platforms allows a remote authenticated attacker holding only the webtools base permissions (OFBTOOLS_VIEW, WEBTOOLS_VIEW) — explicitly not the ENTITY_MAINT permission the export feature declares and visibly refuses to…
When was the CVE record for CVE-2026-82916 published?
The CVE record for CVE-2026-82916 was published on November 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-82916 actively exploited?
CVE-2026-82916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82916?
CVE-2026-82916 has a CVSS v3.1 base score of 7.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-82916?
The CVE record for CVE-2026-82916 names the fix: "Users are recommended to upgrade to version 24.09.08, which fixes this issue." The vendor advisories EchelonGraph has for CVE-2026-82916 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82916?

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

Book a Demo →Browse All CVEs