# CVE-2026-10532: Logback deserialization whitelist bypass for Proxy objects

> Attackers can bypass deserialization restrictions in Logback to instantiate Proxy objects, though remote code execution is not currently identified.

- **Severity:** Low 2.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:P/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** CLEANSTART-2026-GG17411, CLEANSTART-2026-GI85197, CLEANSTART-2026-IG09233, CLEANSTART-2026-YH31321, CLEANSTART-2026-YY39100, CLSA-2026-1784682821, CLSA-2026-1792693506, DEBIAN-CVE-2026-10532, ECHO-1df5-f9ba-f1d0, GHSA-jhq6-gfmj-v8fx, MINI-2wpp-ch7c-gx7j, MINI-3q4g-mxr8-6hw8, MINI-5qgp-8mmp-3gq9, MINI-68w9-j2f5-gcw6, MINI-7cj5-q78x-gpj2, MINI-8q9v-jgmf-h6wp, MINI-f3fh-7hv9-hj24, MINI-f7jj-m7vm-j9v7, MINI-g8hc-f45m-pw5m, MINI-j99p-9999-r266, MINI-mfjc-4wxh-qf29, MINI-mq7w-9hmc-q3j2, MINI-pw58-24qv-gc49, MINI-q786-773x-pfj5, MINI-rq95-97g6-cq9r, MINI-v2v3-cg8j-52pp, MINI-w73v-9q66-85jg, MINI-wmg3-f5m4-fqh2, MINI-xc6m-pw24-87h4, RHLW-2026-666a4e7d1066f856, RHLW-2026-96d3ee80fb77c7d0, UBUNTU-CVE-2026-10532, openSUSE-SU-2026:10999-1

## What is CVE-2026-10532?

CVE-2026-10532 is a low-severity unsafe deserialization vulnerability in QOS.CH Sarl logback, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-10532?

2 open source packages ship an affected version, including ch.qos.logback:logback-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ch.qos.logback:logback-core` | Maven | All versions | 1.5.34 |
| `ch.qos.logback:logback-core` | Maven | All versions | 1.5.34 |
| `logback` | openSUSE:Tumbleweed | All versions | 1.5.34-1.1 |

## How do I fix CVE-2026-10532?

Upgrade ch.qos.logback:logback-core to 1.5.34 or later.

## Is CVE-2026-10532 being exploited?

There is no known exploitation of CVE-2026-10532 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10532 and fix it if it is affected.

What it is: CVE-2026-10532 is a low-severity unsafe deserialization vulnerability in QOS.CH Sarl logback, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10532 in the wild and no public exploit code.

Affected packages and fixed versions:
- ch.qos.logback:logback-core (Maven): affected all versions; fixed in 1.5.34
- ch.qos.logback:logback-core (Maven): affected all versions; fixed in 1.5.34

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10532/ (Markdown: https://insights.sbomify.com/CVE-2026-10532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10532
- OSV: https://osv.dev/vulnerability/CVE-2026-10532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10532/
Summaries are generated and may contain mistakes; the official description above is the record.