Security readout for executives and security teams
Plain-English summary
CVE-2026-24802 affects briandilley/jsonrpc4j through 1.6.0. The public description points to an infinite loop in NoCloseOutputStream.java, which could reduce availability or reliability when triggered. Severity is medium, and no active exploitation is indicated by the provided sources.
Executive priority
Treat as a moderate availability and reliability risk. Prioritize validation in externally reachable or critical services, but do not assume emergency exploitation pressure without new evidence of active attacks.
Technical view
The CVE describes CWE-835, a loop with an unreachable exit condition, in jsonrpc4j src/main/java/com/googlecode/jsonrpc4j modules, specifically NoCloseOutputStream.java. CVSS 4.0 score is 5.3 with network attack vector, low complexity, no privileges required, and passive user interaction. A GitHub pull request is referenced as a patch source.
Likely exposure
Organizations may be exposed if applications directly or transitively use briandilley/jsonrpc4j versions through 1.6.0. Exposure depends on whether affected jsonrpc4j code paths are reachable in deployed services.
Exploitation context
The sources do not report exploitation in the wild, and the CVE is not marked KEV. Based on CVSS, exploitation is network-reachable and low-complexity, but requires passive user interaction. The practical trigger conditions are not fully described publicly.
Researcher notes
The source bundle has a title mismatch: it says buffer overflow, while the description and CWE indicate an infinite loop. Affected-version data is also sparse. Further confirmation from the upstream PR and release artifacts is needed before asserting a fixed version.
Mitigation direction
- Inventory applications and dependencies for briandilley/jsonrpc4j through 1.6.0.
- Review GitHub PR #333 and vendor project guidance for the patch status.
- Upgrade or patch when a validated fixed release or vendor-supported change is available.
- Prioritize internet-facing or business-critical services using jsonrpc4j.
Validation and detection
- Check dependency manifests and SBOMs for jsonrpc4j versions through 1.6.0.
- Confirm whether affected jsonrpc4j code paths are used in deployed applications.
- Review runtime logs for unexplained hangs or resource exhaustion in services using jsonrpc4j.
- Track vendor repository updates and release notes tied to PR #333.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-835: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24802 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:L/AU:Y/R:A/V:D/RE:M/U:Amber
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:L/AU:Y/R:A/V:D/RE:M/U:Amber——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:L/AU:Y/R:A/V:D/RE:M/U:Amber
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/briandilley/jsonrpc4j/pull/333CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.