How severe is CVE-2006-7197?

No CVSS score has been assigned to CVE-2006-7197 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-7197?

CVE-2006-7197 affects the following packages: org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2006-7197?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2006-7197. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2006-7197 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2006-7197 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2006-7197 actively exploited in the wild?

No public exploit code has been indexed for CVE-2006-7197 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2006-7197?

CVE-2006-7197 has an EPSS (Exploit Prediction Scoring System) score of 8.3%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2006-7197 published, and has it been updated?

CVE-2006-7197 was published on May 1, 2022 and was last updated on April 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2006-7197 — tomcat

CVE-2006-7197 is a security vulnerability in org.apache.tomcat:tomcat. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Apache Tomcat Buffer Over-Read

Published

May 1, 2022

Updated

Apr 9, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The AJP connector in Apache Tomcat 5.5.15 uses an incorrect length for chunks, which can cause a buffer over-read in the ajp_process_callback in mod_jk, which allows remote attackers to read portions of sensitive memory.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

tomcatapache

1 version

5.5.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2006-7197. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Network Satellite Server v 4.2	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0524
Red Hat Network Satellite Server v 5.0	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0261

Frequently Asked Questions

The AJP connector in Apache Tomcat 5.5.15 uses an incorrect length for chunks, which can cause a buffer over-read in the `ajp_process_callback` in mod_jk, which allows remote attackers to read portions of sensitive memory.

O3 Security · Impact-Aware SCA

Is CVE-2006-7197 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works