Logback vulnerable to Object Injection through HardenedObjectInputStream modules

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-10532: 0.37% estimated exploitation activity in the next 30 days; percentile 30.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

1 Jun 2026, 15:30 UTC

Last modified by the source

15 Jul 2026, 21:52 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jhq6-gfmj-v8fx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-10532

Advisory: Logback vulnerable to Object Injection through HardenedObjectInputStream modules
IDs: CVE-2026-10532, GHSA-jhq6-gfmj-v8fx
Record: https://patchnext.com/advisories/cve-2026-10532 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ch.qos.logback:logback-core 1.5.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven ch.qos.logback:logback-core: affected < 1.5.34; fixed in 1.5.34

## Suggested inspection (read-only)
- Maven ch.qos.logback:logback-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ch.qos.logback:logback-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jhq6-gfmj-v8fx (GitHub-reviewed advisory GHSA-jhq6-gfmj-v8fx lists affected ranges: Maven ch.qos.logback:logback-core >=0 <1.5.34)

Commands are suggestions: review each one before running it.