How severe is CVE-2024-12801?

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

Which packages are affected by CVE-2024-12801?

CVE-2024-12801 affects the following packages: ch.qos.logback:logback-core (Maven), ch.qos.logback:logback-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-12801?

Update ch.qos.logback:logback-core to 1.5.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12801 is resolved across your whole dependency graph.

How do I detect CVE-2024-12801 in my Maven dependencies?

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2024-12801 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-12801 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-2024-12801?

CVE-2024-12801 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th 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.

What type of vulnerability is CVE-2024-12801?

CVE-2024-12801 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-12801 published, and has it been updated?

CVE-2024-12801 was published on December 19, 2024 and was last updated on April 10, 2026. 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-2024-12801 — logback-core

Fix: qos-ch/logback@5f05041

CVE-2024-12801 is a Server-Side Request Forgery (SSRF) vulnerability in ch.qos.logback:logback-core. A fix is available for ch.qos.logback:logback-core — see the affected versions and patch details below.

QOS.CH logback-core Server-Side Request Forgery vulnerability

Also known asGHSA-6v67-2wr5-gvf4

Published

Dec 19, 2024

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-12801.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕ch.qos.logback:logback-core☕ch.qos.logback:logback-core

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

Server-Side Request Forgery (SSRF) in SaxEventRecorder by QOS.CH logback version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 on the Java platform, allows an attacker to forge requests by compromising logback configuration files in XML.

The attacks involves the modification of DOCTYPE declaration in XML configuration files.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ch.qos.logback:logback-core`	≥ 1.4.0&&< 1.5.13	1.5.13`ch.qos.logback:logback-core:1.5.13`
☕Maven	`ch.qos.logback:logback-core`	all versions	1.3.15`ch.qos.logback:logback-core:1.3.15`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ch.qos.logback:logback-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ch.qos.logback:logback-core to 1.5.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12801 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.