CVE-2026-53582

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-102112 (ENISA EUVD)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.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.10, the Trust module stores attacker-controlled certificate authority and certificate refid values and interpolates them into XPath expressions in src/opnsense/mvc/app/models/OPNsense/Trust/FieldTypes/CAsField.php and src/opnsense/mvc/app/models/OPNsense/Trust/FieldTypes/CertificatesField.php. A user with CA Manager or Certificate Manager privileges can submit a crafted refid and repeatedly retrieve the object to obtain a boolean refcount oracle, allowing values in config.xml to be recovered character by character. Exposed values can include password hashes, API credentials, certificate private keys, VPN key material, and high-availability credentials, enabling privilege escalation and compromise of other security domains. This issue is fixed in version 26.1.10.

CVSS v3
7.1
EG Score
7.1HIGHmedium 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.7% × 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
54th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 15, 2026
Fix named in the CVE record. Sources: github, github_commit.
Web page

Full Disclosure: OPNsense XPATH Injection (CVE-2026-53582)

http://seclists.org/fulldisclosure/2026/Jul/18
GitHub commit

commit fc2f0d745c17 (opnsense/core)

Fix landed in opnsense/core commit fc2f0d745c17 — awaiting tagged release

https://github.com/opnsense/core/commit/fc2f0d745c17855d2027b192fd4e3fa913e26859
GitHub commit

commit e2cd06734351 (opnsense/core)

Fix landed in opnsense/core commit e2cd06734351 — awaiting tagged release

https://github.com/opnsense/core/commit/e2cd067343511252fb0d391a17d82d3ecceece45
GitHub advisoryMentions a patch (unverified)

XPATH Injection can disclose any secret in config.xml · Advisory · opnsense/core · GitHub

https://github.com/opnsense/core/security/advisories/GHSA-xww7-76m6-mh2r

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-10-29 20:09 UTCEG score recompute
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-25 14:20 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-23 07:21 UTCEG score recompute
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-18 03:31 UTCEG score recompute
  19. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-16 18:30 UTCEG score recompute
  21. 2026-10-16 17:22 UTCEG score recompute
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-15 16:30 UTCEG score recompute
  24. 2026-10-15 15:23 UTCEG score recomputeFirst assessed: 7.1 HIGH
  25. 2026-10-15 15:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53582?
CVE-2026-53582 is a high-severity vulnerability; its CVE record was published on October 15, 2026. OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.10, the Trust module stores attacker-controlled certificate authority and certificate refid values and interpolates them into XPath expressions in src/opnsense/mvc/app/models/OPNsense/Trust/FieldTypes/CAsField.php and…
When was the CVE record for CVE-2026-53582 published?
The CVE record for CVE-2026-53582 was published on October 15, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-53582 actively exploited?
CVE-2026-53582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53582?
CVE-2026-53582 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53582?
The CVE record for CVE-2026-53582 names the fix: "This issue is fixed in version 26.1.10."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53582?

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