CVE-2006-7196

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 1,582 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS: 72%CVSS: Exploit: NoneExposed: 1,582

A fix is available — apply it.

Cross-site scripting (XSS) vulnerability in the calendar application example in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.31, 5.0.0 through 5.0.30, and 5.5.0 through 5.5.15 allows remote attackers to inject arbitrary web script or HTML via the time parameter to cal2.jsp and possibly unspecified other vectors. NOTE: this may be related to CVE-2006-0254.1.

Live · internet exposure

1,582 internet-exposed hosts are running an affected version of CVE-2006-7196 right now.

across 82 countries (China, United States, Korea, Republic of, Germany, India)top: tomcat
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
EG Score
0.0(none)
EPSS
99.4%
KEV
Not listed

Published

May 10, 2007

Last Modified

April 23, 2026

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhattomcat5-0:5.0.30-0jpp_10rh2008-06-30redhat
redhattomcat5-0:5.5.23-0jpp_4rh.32007-05-21redhat
redhattomcat5-0:5.0.30-0jpp_5rh2007-05-08redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat:tomcat5.5.16

All Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 2× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-08 15:09 UTCEPSS rescore
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-04 06:27 UTCEPSS rescore
  4. 2026-07-04 06:26 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-28 14:02 UTCEPSS rescore
  8. 2026-06-28 04:52 UTCEPSS rescore
  9. 2026-06-25 13:46 UTCEPSS rescore
  10. 2026-06-25 13:46 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-24 14:01 UTCEPSS rescore
  13. 2026-06-23 21:29 UTCEPSS rescore
  14. 2026-06-23 21:29 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-21 01:56 UTCEPSS rescore
  17. 2026-06-21 01:56 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-12 23:08 UTCEPSS rescore
Show 26 more
  1. 2026-06-08 14:13 UTCEPSS rescore
  2. 2026-06-07 15:21 UTCEPSS rescore
  3. 2026-06-07 15:21 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-06 13:44 UTCEPSS rescore
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 06:07 UTCEPSS rescore
  9. 2026-06-02 20:10 UTCEPSS rescore
  10. 2026-06-02 20:10 UTCEPSS rescore
  11. 2026-06-01 13:49 UTCEPSS rescore
  12. 2026-06-01 13:49 UTCEPSS rescore
  13. 2026-05-31 02:48 UTCEG score recompute
  14. 2026-05-31 02:48 UTCVendor advisory
  15. 2026-05-31 00:13 UTCEPSS rescore
  16. 2026-05-31 00:13 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-20 22:36 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-20 11:20 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore
  26. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-30563✓ verified
    First seen Sep 4, 2007

    Apache Tomcat 5.5.15 - cal2.jsp Cross-Site Scripting

    Open source ↗

Frequently asked(4)

What is CVE-2006-7196?
CVE-2006-7196 is a none vulnerability published on May 10, 2007. Cross-site scripting (XSS) vulnerability in the calendar application example in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.31, 5.0.0 through 5.0.30, and 5.5.0 through 5.5.15 allows remote attackers to inject arbitrary web script or HTML via the time parameter to cal2.jsp and possibly…
When was CVE-2006-7196 disclosed?
CVE-2006-7196 was first published in the National Vulnerability Database on May 10, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-7196 actively exploited?
CVE-2006-7196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2006-7196?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-7196, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-7196

Explore →

Is Your Infrastructure Affected by CVE-2006-7196?

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