JavaCV: Integer Overflow in IPCameraFrameGrabber Causes Infinite-Loop DoS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-102834: 0.50% estimated exploitation activity in the next 30 days; percentile 43.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary IPCameraFrameGrabber parses the Content-Length value from the multipart MJPEG HTTP stream returned by the configured IP camera without any bounds checking. A malicious or compromised camera endpoint - or any network attacker able to tamper with the plaintext HTTP response (these streams are conventionally accessed over http://, as documented in the class itself) - can supply a Content-Length value in the range 1073741825-2147483647. This drives the internal buffer-growth routine ensureBufferCapacity(int) into 32-bit signed integer overflow, which turns the "grow the buffer" loop into a true infinite loop: the loop variable oscillates to 0 and never again satisfies the loop's exit condition. The thread that called grab()/grabBufferedImage() spins at 100% CPU forever and never returns, permanently hanging the calling application's frame-grabbing thread with no exception, timeout, or interrupt path available to the caller. Details File:…

Published by the source

16 Oct 2026, 19:53 UTC

Last modified by the source

16 Oct 2026, 20:00 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rxjv-24xq-76wc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rxjv-24xq-76wc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102834

Advisory: JavaCV: Integer Overflow in IPCameraFrameGrabber Causes Infinite-Loop DoS
IDs: CVE-2026-102834, GHSA-rxjv-24xq-76wc
Record: https://patchnext.com/advisories/cve-2026-102834 (revision 2, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.bytedeco:javacv 1.5.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.bytedeco:javacv: affected < 1.5.14; fixed in 1.5.14

## Suggested inspection (read-only)
- Maven org.bytedeco:javacv: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.bytedeco:javacv.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rxjv-24xq-76wc (OSV record GHSA-rxjv-24xq-76wc lists affected ranges: Maven org.bytedeco:javacv >=0 <1.5.14 (fixed))
- Verified: https://github.com/advisories/GHSA-rxjv-24xq-76wc (GitHub-reviewed advisory GHSA-rxjv-24xq-76wc lists affected ranges: Maven org.bytedeco:javacv >=0 <1.5.14)

Commands are suggestions: review each one before running it.