CVE-2026-74048

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-105004 (ENISA EUVD) · GHSA-38jj-69cp-9wgc (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activation fails, Tomcat logs and error but continues to use JSSE in non-FIPS mode with the provided configuration.

This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.26, from 10.1.22 through 10.1.60, from 9.0.92 through 9.0.122.

Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
39th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.4% 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.

A fix is available. 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 20, 2026

Last Modified

October 29, 2026

Advisory Details (2)

Auto-updated Oct 29, 2026
Patch available.
Web page

oss-security - CVE-2026-74048: Apache Tomcat: OpenSSL-FFM FIPS failure does not prevent start-up

http://www.openwall.com/lists/oss-security/2026/10/20/21

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhattomcat10-main-10.1.61-0.1.hum12026-10-20redhat
redhattomcat11-main-11.0.27-0.1.hum12026-10-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 3 ecosystems)
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.40-1 ... 10.1.60-1 (11 versions)
  • every version on: no fix on record
—
tomcat1111.0.11-1 ... 11.0.6-1 (10 versions)
  • every version on: no fix on record
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.40-1 ... 10.1.60-1 (11 versions)
  • every version on: no fix on record
—
tomcat1111.0.11-1 ... 11.0.6-1 (10 versions)
  • every version on: no fix on record
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.10-1 ... 10.1.9-1 (37 versions)
  • every version on: no fix on record
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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-13 16:57 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  5. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  10. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  11. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  12. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  13. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  14. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  15. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  16. 2026-10-29 18:27 UTCVendor advisory
  17. 2026-10-29 18:27 UTCGHSA enrichmentGHSA-38jj-69cp-9wgc
  18. 2026-10-29 17:55 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  19. 2026-10-29 17:55 UTCVendor advisory
  20. 2026-10-29 17:54 UTCGHSA enrichmentGHSA-38jj-69cp-9wgc
  21. 2026-10-29 17:51 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  22. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 14 more
  1. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-25 14:04 UTCEchelonGraph re-scored
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-10-20 19:47 UTCGHSA enrichmentGHSA-38jj-69cp-9wgc
  8. 2026-10-20 19:26 UTCGHSA enrichmentGHSA-38jj-69cp-9wgc
  9. 2026-10-20 19:25 UTCNVD update
  10. 2026-10-20 18:31 UTCGHSA enrichmentGHSA-38jj-69cp-9wgc
  11. 2026-10-20 18:27 UTCMITRE cvelistV5
  12. 2026-10-20 14:25 UTCNVD update
  13. 2026-10-20 13:54 UTCEchelonGraph re-scored
  14. 2026-10-20 13:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74048?
CVE-2026-74048 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activation fails, Tomcat logs and error but continues to use JSSE in non-FIPS mode with the provided configuration. This issue affects Apache Tomcat: from…
When was the CVE record for CVE-2026-74048 published?
The CVE record for CVE-2026-74048 was published on October 20, 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-74048 actively exploited?
CVE-2026-74048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74048?
CVE-2026-74048 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-74048?
A fix for CVE-2026-74048 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74048 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-74048

Explore →

Is Your Infrastructure Affected by CVE-2026-74048?

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