NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

logback serialization vulnerabilityGHSA-vmq6-5m68-f53m

HIGHFix: qos-ch/logback@9c782b4

GHSA-vmq6-5m68-f53m is a high-severity (CVSS 7.1) Deserialization of Untrusted Data vulnerability in ch.qos.logback:logback-classic. A fix is available for ch.qos.logback:logback-classic — see the affected versions and patch details below.

Also known asCVE-2023-6378
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Nov 6, 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 GHSA-vmq6-5m68-f53m.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.11%0.54%0.97%1.40%0.6%0.9%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected
☕ch.qos.logback:logback-classic☕ch.qos.logback:logback-classic☕ch.qos.logback:logback-core☕ch.qos.logback:logback-core☕ch.qos.logback:logback-core☕ch.qos.logback:logback-classic

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

A serialization vulnerability in logback receiver component part of logback allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.

This is only exploitable if logback receiver component is deployed. See https://logback.qos.ch/manual/receivers.html

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavench.qos.logback:logback-classic≥ 1.3.0&&< 1.3.121.3.12ch.qos.logback:logback-classic:1.3.12
☕Mavench.qos.logback:logback-classic≥ 1.4.0&&< 1.4.121.4.12ch.qos.logback:logback-classic:1.4.12
☕Mavench.qos.logback:logback-core≥ 1.3.0&&< 1.3.121.3.12ch.qos.logback:logback-core:1.3.12
☕Mavench.qos.logback:logback-core≥ 1.4.0&&< 1.4.121.4.12ch.qos.logback:logback-core:1.4.12
☕Mavench.qos.logback:logback-coreall versions1.2.13ch.qos.logback:logback-core:1.2.13
☕Mavench.qos.logback:logback-classicall versions1.2.13ch.qos.logback:logback-classic:1.2.13

Affected Products

1 product · 3 configurations
Application
logbackqos
≥ 1.4.0 && < 1.4.12
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update ch.qos.logback:logback-classic to 1.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmq6-5m68-f53m is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The Logback package vulnerability, posing a risk of denial-of-service through a serialization flaw in its receiver component, is considered a moderate issue due to its potential impact on system availability. While denial-of-service vulnerabilities can be disruptive, the severity is tempered by the fact that they…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-vmq6-5m68-f53m (CC BY 4.0)
ProductFixed inAdvisory
Red Hat AMQ Broker 7logbackRHSA-2024:2945
Red Hat Fuse 7.13.0logbackRHSA-2024:3354
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/server-rhel8:3.15-3RHSA-2024:4631
RHINT Camel-Springboot 4.0.3logbackRHSA-2024:0793

Frequently Asked Questions

A serialization vulnerability in logback receiver component part of logback allows an attacker to mount a Denial-Of-Service attack by sending poisoned data. This is only exploitable if logback receiver component is deployed. See https://logback.qos.ch/manual/receivers.html
O3 Security · Impact-Aware SCA

Is GHSA-vmq6-5m68-f53m in your dependencies?

Find it across Maven, including transitive dependencies.

GHSA-vmq6-5m68-f53m: logback-classic — Fixed in 1.3.12