CVE-2026-10532: Logback deserialization whitelist bypass for Proxy objects
Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream (logback-core) modules) allows Object Injection, albeit heavily restricted.
More precisely, an attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate Proxy objects.
Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions.
This issue affects logback: through 1.5.33 inclusive.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
logback/logback-core (HardenedObjectInputStream)to a version that resolves this vulnerability.Fixed in 1.5.34
Event History
Frequently Asked Questions
What is the severity of CVE-2026-10532?
The severity of CVE-2026-10532 is classified as low with a CVSS score of 2.9.
How do I fix CVE-2026-10532?
To fix CVE-2026-10532, you should upgrade to logback version 1.5.34.
What kind of vulnerability is CVE-2026-10532?
CVE-2026-10532 is a deserialization of untrusted data vulnerability that allows Object Injection.
What software is affected by CVE-2026-10532?
CVE-2026-10532 affects the logback-core modules within the QOS.CH Sarl logback framework.
How can an attacker exploit CVE-2026-10532?
An attacker can exploit CVE-2026-10532 by influencing serialized data sent to SimpleSocketServer or SimpleSSLSocketServer.