Skip to main content
CVE-2025-2529VulnerabilityPublished

CVE-2025-2529: IBM Terracotta · Improper Handling of Syntactically Invalid Structure

Affects IBM TerracottaSource CVE Database V5

0

Not known to be exploited · CVSS 2.9 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.ehcache/ehcachepkg:maven/org.ehcache/ehcacheOther threatsAffected
  • =10.15.0
  • =11.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-2529, organizations should implement strict input validation and sanitization of all cache keys sourced from external or untrusted parties. Applying salting or hashing to keys before caching can prevent malformed or malicious keys from causing performance degradation. Monitoring cache performance metrics to detect anomalies early is recommended. Where possible, upgrade to later versions of IBM Terracotta Ehcache once patches addressing this issue are released. Additionally, limit local access to systems running affected versions to reduce attack surface. Incorporate caching best practices such as key normalization and size limits to avoid resource exhaustion. Conduct thorough testing of cache behavior under load with external inputs to identify potential performance bottlenecks.

Description

Applications using affected versions of Ehcache 3.x can experience degraded cache-write performance if the application using Ehcache utilizes keys sourced from (malicious) external parties in an unfiltered/unsalted way.

References

Community reviews

Loading reviews…