Exploited CVEs / Apache / CVE-2026-34486

CVE-2026-34486

Apache Tomcat Missing Encryption of Sensitive Data Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-08-07 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV
7.5
CVSS base
83%
EPSS exploit probability
High
Severity
2026-08-04
Added to KEV
2026-08-07 (past due)
CISA due date

Actively exploited Apache Tomcat vulnerability, High severity, CVSS 7.5. Added to the CISA KEV catalog 2026-08-04.

CISA required actionOfficial fix for CVE-2026-34486Admin questions#22 hottest CVE right now
Senserva AI Opinion and rich prompt for CVE-2026-34486

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-08-07; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-34486

Published
2026-08-04
Last revised
2026-08-04
Changes tracked
2

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is CISA KEV listing on 2026-08-04, confirming active exploitation, alongside EPSS climbing from 42.6% to 81.2% by 2026-08-05 and reaching 82.9% on 2026-08-11. Severity peaked at 9.8 on 2026-08-05 before settling to 7.5 on 2026-08-07. Exploitation risk stays high and rising, so prioritize remediation today.

0%25%50%75%100%CISA KEVCISA KEV on 2026-08-042026-08-04: EPSS 43%2026-08-04: EPSS 43%2026-08-05: EPSS 81%2026-08-05: EPSS 81%2026-08-07: EPSS 81%2026-08-07: EPSS 81%2026-08-11: EPSS 83%2026-08-11: EPSS 83%2026-08-12: EPSS 83%EPSS 83%2026-08-042026-08-12

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-08-04 CVSS 0.0 to 7.5; EPSS first scored at 42.6%; added to the CISA KEV catalog by CISA
  • 2026-08-05 CVSS 7.5 to 9.8; EPSS 42.6% to 81.2%
  • 2026-08-07 CVSS 9.8 to 7.5
  • 2026-08-11 EPSS 81.2% to 82.9%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-08-07 (past due).

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Official fix for CVE-2026-34486

Check the vendor's security advisory channel for the patched Tomcat versions and workarounds.

Common questions about CVE-2026-34486

Is CVE-2026-34486 actively exploited?

Yes. CVE-2026-34486 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-08-04, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 83%.

What is the CISA deadline and required action for CVE-2026-34486?

CISA set the federal (BOD 22-01) remediation due date at 2026-08-07, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What fixes CVE-2026-34486?

Check the vendor's security advisory for the patched Tomcat versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-34486?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-34486's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.