CVE-2026-57155

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th 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
Elevated

Also known asEUVD-2026-102114 (ENISA EUVD)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.9Exploit: No code on recordExposed 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.11, the Firewall Alias GeoIP importer's process_zip() and process_gzip() paths in src/opnsense/scripts/filter/lib/alias/geoip.py use an unvalidated CSV country_code value to construct output filenames below /usr/local/share/GeoIP/alias. A user with Firewall Alias Edit privilege can configure an attacker-controlled GeoIP source URL and supply an archive whose country code traverses into another existing directory, causing attacker-controlled content to be written as root with an -IPv4 or -IPv6 suffix. A crafted newsyslog fragment and oversized log file can use the default hourly root cron job to execute commands as root, resulting in complete firewall compromise. This issue is fixed in version 26.1.11.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-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.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 15, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Root RCE via Arbitrary File Write in GeoIP Alias Importer · Advisory · opnsense/core · GitHub

https://github.com/opnsense/core/security/advisories/GHSA-wjqq-rfmm-v5h3
Web page🟡 PoC Available

Chasing the OPNsense RCE: The Story Behind My First CVEs (CVE-2026-57155) | HackerAsk

https://hackerask.com/posts/opnsense
GitHub commit

commit e7fbfaa7f5e0 (opnsense/core)

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

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

commit c46aced9c47d (opnsense/core)

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

https://github.com/opnsense/core/commit/c46aced9c47d956167e294911113bc334fea5f48

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 40× 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:57 UTCEG score recompute
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-31 19:11 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-30 21:22 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-29 23:35 UTCEG score recompute
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-29 01:48 UTCEG score recompute
  10. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-28 04:00 UTCEG score recompute
  12. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-10-27 05:59 UTCEG score recompute
  14. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  15. 2026-10-26 04:06 UTCEG score recompute
  16. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  17. 2026-10-25 14:17 UTCEG score recompute
  18. 2026-10-25 06:19 UTCEG score recompute
  19. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-24 08:32 UTCEG score recompute
  21. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-23 10:45 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-22 12:44 UTCEG score recompute
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
Show 15 more
  1. 2026-10-21 14:56 UTCEG score recompute
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  3. 2026-10-19 17:43 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  5. 2026-10-18 19:54 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  7. 2026-10-18 03:29 UTCEG score recompute
  8. 2026-10-17 22:06 UTCEG score recompute
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-17 00:15 UTCEG score recompute
  11. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-15 16:29 UTCEG score recompute
  13. 2026-10-15 15:50 UTCEG score recompute
  14. 2026-10-15 15:23 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  15. 2026-10-15 15:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57155?
CVE-2026-57155 is a critical-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.11, the Firewall Alias GeoIP importer's process_zip() and process_gzip() paths in src/opnsense/scripts/filter/lib/alias/geoip.py use an unvalidated CSV country_code value to construct output filenames below…
When was the CVE record for CVE-2026-57155 published?
The CVE record for CVE-2026-57155 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-57155 actively exploited?
CVE-2026-57155 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-57155?
CVE-2026-57155 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57155?
The CVE record for CVE-2026-57155 names the fix: "This issue is fixed in version 26.1.11."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57155?

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

Book a Demo →Browse All CVEs