CVE-2026-63442

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st 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-102138 (ENISA EUVD)Source: ENISA EUVD

8.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.3%CVSS: 8.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.11, the unauthenticated WebGUI login usernamefld accepts carriage-return and line-feed characters that survive LOG_AUTH processing through syslog-ng-lockout.conf into the syslog-ng program destination feeding lockout_handler. The consumer's readline() processing treats an injected fragment as a separate authentication event and selects the first syntactically valid IP address from the forged line. An attacker with network access to the login page can forge failure events for another IP, causing that IP to be added to the sshlockout PF table and its active states to be killed, or forge accepted events that reset an attacker's own brute-force counter. This can block administrative, DNS, gateway, or monitoring addresses and can bypass password-guessing lockout without authentication. This issue is fixed in version 26.1.11.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
21st
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 (3)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit c930ab586ffe (opnsense/core)

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

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

commit 8bdaad95f405 (opnsense/core)

Fix landed in opnsense/core commit 8bdaad95f405 — awaiting tagged release

https://github.com/opnsense/core/commit/8bdaad95f405f4587bb83bf35aa652ca493cc2a4
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Log Forgery via Login Username CRLF in WebGUI Authentication → Pf Table IP Blocking · Advisory · opnsense/core · GitHub

https://github.com/opnsense/core/security/advisories/GHSA-2v2x-m4j7-76pv

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 26× 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:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-31 15:54 UTCEG score recompute
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-25 14:13 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-24 05:12 UTCEG score recompute
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-18 03:23 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-16 18:30 UTCEG score recompute
  22. 2026-10-16 17:22 UTCEG score recompute
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-15 16:32 UTCEG score recompute
  25. 2026-10-15 15:38 UTCEG score recomputeFirst assessed: 8.1 HIGH
Show 1 more
  1. 2026-10-15 15:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63442?
CVE-2026-63442 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.11, the unauthenticated WebGUI login usernamefld accepts carriage-return and line-feed characters that survive LOG_AUTH processing through syslog-ng-lockout.conf into the syslog-ng program destination feeding…
When was the CVE record for CVE-2026-63442 published?
The CVE record for CVE-2026-63442 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-63442 actively exploited?
CVE-2026-63442 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63442?
CVE-2026-63442 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63442?
The CVE record for CVE-2026-63442 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-63442

Explore →

Is Your Infrastructure Affected by CVE-2026-63442?

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

Book a Demo →Browse All CVEs