How severe is CVE-2026-24802?

No CVSS score has been assigned to CVE-2026-24802 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-24802?

CVE-2026-24802 affects the following packages: com.github.briandilley.jsonrpc4j:jsonrpc4j (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-24802?

Update com.github.briandilley.jsonrpc4j:jsonrpc4j to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-24802 is resolved across your whole dependency graph.

How do I detect CVE-2026-24802 in my Maven dependencies?

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

How do I mitigate CVE-2026-24802 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-24802 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-24802 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 CVE-2026-24802?

CVE-2026-24802 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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 CVE-2026-24802?

CVE-2026-24802 is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-24802 published, and has it been updated?

CVE-2026-24802 was published on January 27, 2026 and was last updated on October 28, 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

Not in CISA KEV

CVE-2026-24802 — jsonrpc4j

Fix: briandilley/jsonrpc4j#333

CVE-2026-24802 is a CWE-835 vulnerability in com.github.briandilley.jsonrpc4j:jsonrpc4j. A fix is available for com.github.briandilley.jsonrpc4j:jsonrpc4j — see the affected versions and patch details below.

Buffer Overflow Vulnerability in briandilley/jsonrpc4j

Also known asGHSA-hcx3-3q5c-r5v6

Published

Jan 27, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

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 CVE-2026-24802.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.github.briandilley.jsonrpc4j:jsonrpc4j

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

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in briandilley jsonrpc4j (src/main/java/com/googlecode/jsonrpc4j modules). This vulnerability is associated with program files NoCloseOutputStream.Java.

This issue affects jsonrpc4j: through 1.6.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.github.briandilley.jsonrpc4j:jsonrpc4j`	all versions	1.7.0`com.github.briandilley.jsonrpc4j:jsonrpc4j:1.7.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.github.briandilley.jsonrpc4j:jsonrpc4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.github.briandilley.jsonrpc4j:jsonrpc4j to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-24802 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-24802 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works