How severe is GHSA-pr98-23f8-jwxv?

No CVSS score has been assigned to GHSA-pr98-23f8-jwxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pr98-23f8-jwxv?

GHSA-pr98-23f8-jwxv affects the following packages: ch.qos.logback:logback-core (Maven), ch.qos.logback:logback-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pr98-23f8-jwxv?

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

How do I detect GHSA-pr98-23f8-jwxv 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-pr98-23f8-jwxv 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-pr98-23f8-jwxv?

O3 pinpoints whether GHSA-pr98-23f8-jwxv 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-pr98-23f8-jwxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-pr98-23f8-jwxv 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-pr98-23f8-jwxv?

GHSA-pr98-23f8-jwxv has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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.

What type of vulnerability is GHSA-pr98-23f8-jwxv?

GHSA-pr98-23f8-jwxv is classified as Expression Language Injection (CWE-917). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pr98-23f8-jwxv published, and has it been updated?

GHSA-pr98-23f8-jwxv was published on December 19, 2024 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.

GHSA-pr98-23f8-jwxv: logback-core Remote Code Execution

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk32th percentile+0.24%

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

2 pkgs affected

☕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

ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core up to and including version 1.5.12 in Java applications allows attackers to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution.

Malicious logback configuration files can allow the attacker to execute arbitrary code using the JaninoEventEvaluator extension.

A successful attack requires the user to have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privilege.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ch.qos.logback:logback-core`	≥ 1.4.0&&< 1.5.13	1.5.13
☕Maven	`ch.qos.logback:logback-core`	all versions	1.3.15

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.5.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr98-23f8-jwxv 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-pr98-23f8-jwxv 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-pr98-23f8-jwxv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core up to and including version 1.5.12 in Java applications allows attackers to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution. Malicious logback configuration files can allow the attacker to execute arbitrary code using the JaninoEventEvaluator extension. A successful attack requires the user to have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious co

O3 Security · Impact-Aware SCA

Is GHSA-pr98-23f8-jwxv in your dependencies?

O3 detects GHSA-pr98-23f8-jwxv 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

GHSA-pr98-23f8-jwxv