CVE-2025-52999VulnerabilityPublished 30 Jul 2025Updated 11 Oct 2026

SUSE · security update for jackson-annotations

Affects SUSESource GCVE Database

Authoritative record:CVE-2025-52999· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade SUSE to 2.15.0 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.15.0

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

bundesamt-f-r-sicherheit-in-de

What to do

Upgrade com.fasterxml.jackson.core/jackson-core to 2.15.0.

Affected software

Product	Affected	Fixed in
Mavencom.fasterxml.jackson.core/jackson-core`pkg:maven/com.fasterxml.jackson.core/jackson-core`Other threats	Affected <2.15.0	Fixed in 2.15.0

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

AI-suggested

An official patch is available from Red Hat to address this vulnerability. Users should follow the vendor's upgrade instructions for Red Hat OpenShift Logging 5.8 as documented at https://docs.openshift.com/container-platform/4.14/logging/cluster-logging-upgrading.html and ensure all prior relevant errata are applied. No additional mitigation steps are indicated by the vendor advisory.

Description

Red Hat Single Sign-On 7.6 is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications. This update to Red Hat Single Sign-On 7.6.12 includes a security update with important impact. Security fixes: * jackson-core: jackson-core Potential StackoverflowError (CVE-2025-52999)

Impact

The vulnerability could lead to a stack overflow condition within the jackson-core library used by Red Hat OpenShift Logging, potentially causing application crashes or denial of service. The advisory does not specify further impact such as remote code execution or data compromise. No known exploits are currently active in the wild.

Summary

CVE-2025-52999 affects Red Hat OpenShift Logging 5.8.22 and related versions, involving a potential stack overflow error in the jackson-core component. This vulnerability is classified under CWE-121 (Stack-based Buffer Overflow). Red Hat has issued an important security advisory (RHSA-2025:17189) confirming the availability of a patch for this issue. The vulnerability impacts versions including 5.8.0 through 5.8.22 and certain 7.x versions as explicitly stated. No active exploitation has been observed. The vendor advisory provides upgrade instructions to remediate the vulnerability.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Aug 2026, 20:45 UTC

WeaknessesCWE-121, CWE-770

Technical details

References

Community reviews

Related threats