How severe is GHSA-gm62-rw4g-vrc4?

GHSA-gm62-rw4g-vrc4 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gm62-rw4g-vrc4?

GHSA-gm62-rw4g-vrc4 affects the following packages: ch.qos.logback:logback-core (Maven), ch.qos.logback:logback-core (Maven), ch.qos.logback:logback-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gm62-rw4g-vrc4?

Update ch.qos.logback:logback-core to 1.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm62-rw4g-vrc4 is resolved across your whole dependency graph.

How do I detect GHSA-gm62-rw4g-vrc4 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gm62-rw4g-vrc4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gm62-rw4g-vrc4?

O3 pinpoints whether GHSA-gm62-rw4g-vrc4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gm62-rw4g-vrc4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gm62-rw4g-vrc4 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 GHSA-gm62-rw4g-vrc4?

GHSA-gm62-rw4g-vrc4 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 48th 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.

When was GHSA-gm62-rw4g-vrc4 published, and has it been updated?

GHSA-gm62-rw4g-vrc4 was published on December 4, 2023 and was last updated on February 4, 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

GHSA-gm62-rw4g-vrc4

HIGH

Logback is vulnerable to an attacker mounting a Denial-Of-Service attack by sending poisoned data

Also known asCVE-2023-6481

Published

Dec 4, 2023

Updated

Feb 4, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk48th percentile+0.46%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

☕ch.qos.logback:logback-core☕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

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ch.qos.logback:logback-core`	≥ 1.4.13&&< 1.4.14	1.4.14
☕Maven	`ch.qos.logback:logback-core`	≥ 1.3.13&&< 1.3.14	1.3.14
☕Maven	`ch.qos.logback:logback-core`	≥ 1.2.12&&< 1.2.13	1.2.13

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ch.qos.logback:logback-core to 1.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm62-rw4g-vrc4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gm62-rw4g-vrc4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gm62-rw4g-vrc4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-gm62-rw4g-vrc4 in your dependencies?

O3 detects GHSA-gm62-rw4g-vrc4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works