CVE-2026-105242

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

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

Score 5.3 from GitHub Security Advisory published 2026-10-06. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Improper Handling of Exceptional Conditions vulnerability in the aspnet-request pattern converter of Apache log4net.

Reading request parameters triggers ASP.NET request validation, so a request carrying content such as markup made the layout throw and the appender discarded the whole event. A sender could suppress the log record of their own request. Only applications on ASP.NET for .NET Framework whose layout uses %aspnet-request are affected.

This issue affects Apache log4net: from 1.2.11 before 3.5.0.

Users are recommended to upgrade to version 3.5.0, which fixes the issue.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
39
EG Risk 39/100

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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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 none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 6, 2026

Last Modified

October 9, 2026

Advisory Details (3)

Auto-updated Oct 6, 2026
Fix named in the CVE record. Sources: github_pr, github_commit.
GitHub commit

commit 145203420c57 (apache/logging-log4net)

Fix landed in apache/logging-log4net commit 145203420c57 — awaiting tagged release

https://github.com/apache/logging-log4net/commit/145203420c579a703008b4b723b6a080757f4964
GitHub pull request

Prevent the ANSI appender and %aspnet-request dropping events

Fix merged in apache/logging-log4net PR #316 on 2026-09-04 — awaiting tagged release

https://github.com/apache/logging-log4net/pull/316

Vendor Advisories for CVE-2026-105242(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
log4net1.2.10+dfsg-10, 1.2.10+dfsg-9
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
log4net1.2.10+dfsg-10, 1.2.10+dfsg-9
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 27× 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-10-11 20:15 UTCEG score recompute
  2. 2026-10-11 16:50 UTCEG score recompute
  3. 2026-10-11 16:50 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  4. 2026-10-11 15:01 UTCEG score recompute
  5. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-10 16:13 UTCEG score recompute
  8. 2026-10-10 16:13 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-09 15:34 UTCEG score recompute
  11. 2026-10-09 15:34 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-08 16:14 UTCEG score recompute
  14. 2026-10-08 16:13 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-07 15:31 UTCEG score recompute
  17. 2026-10-07 15:31 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  18. 2026-10-07 14:52 UTCEG score recompute
  19. 2026-10-07 14:52 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  20. 2026-10-07 13:46 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  21. 2026-10-07 07:28 UTCEG score recompute
  22. 2026-10-07 07:28 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  23. 2026-10-07 06:23 UTCEG score recompute
  24. 2026-10-07 06:23 UTCGHSA enrichmentGHSA-r886-mf8r-26c7 · GitHub CVSS 5.3
  25. 2026-10-06 20:32 UTCEG score recompute
Show 2 more
  1. 2026-10-06 19:58 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  2. 2026-10-06 19:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105242?
CVE-2026-105242 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Improper Handling of Exceptional Conditions vulnerability in the aspnet-request pattern converter of Apache log4net. Reading request parameters triggers ASP.NET request validation, so a request carrying content such as markup made the layout throw and the appender discarded the whole event. A…
When was the CVE record for CVE-2026-105242 published?
The CVE record for CVE-2026-105242 was published on October 6, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-105242 actively exploited?
CVE-2026-105242 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105242?
CVE-2026-105242 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105242?
The CVE record for CVE-2026-105242 names the fix: "Users are recommended to upgrade to version 3.5.0, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-105242 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-105242

Explore →

Is Your Infrastructure Affected by CVE-2026-105242?

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