ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-102834

JavaCV: Integer Overflow in IPCameraFrameGrabber Causes Infinite-Loop DoS

Published Oct 16, 2026 · catalog updated Oct 16, 2026 · JavaCV: Integer Overflow in

Check if you run it

No confirmed exploitation is on record for CVE-2026-102834. EPSS is 0.34%. Act only if a listed version of JavaCV: Integer Overflow in is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (JavaCV: Integer Overflow in).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Version ranges on file
Affected products
Maven org.bytedeco:javacv · maven org.bytedeco · maven org.bytedeco:javacv

### Summary parses the 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 , as documented in the class itself) - can supply a value in the range - . This drives the internal buffer-growth routine into 32-bit signed integer overflow, which turns the "grow the buffer" loop into a true infinite loop: the loop variable oscillates to and never again satisfies the loop's exit condition. The thread that called / 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: is taken verbatim from the HTTP response headers of the camera stream and passed directly into with no upper-bound validation (the comment "adaptive size - careful - don't want a 2G jpeg" shows the author was aware of the risk but never implemented a check). repeatedly doubles (a 32-bit , starting at ) until it is . If is greater than ( ) but ( ): 1. reaches ( ) after 20 doublings; the loop condition is still true. 2. computes , which overflows a signed 32-bit and wraps to ( ). 3. The loop condition (a negative number compared to a large positive ) is still true, so the loop continues. 4. computes , which in two's-complement 32-bit arithmetic wraps to . 5. From this point on, is permanently ( ), and remains true forever - the loop never terminates. This is a pure CPU-bound loop with no I/O, no blocking call, and no check, so it cannot be interrupted via and will not respect any / configured on the grabber (those only apply to the socket read that happens *before* this code path). The only remedy is killing the JVM/thread from outside. ### PoC A minimal malicious/MITM'd MJPEG server that reproduces the hang: Java client (representative of any applic

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Maven org.bytedeco:javacv0 → 1.5.14
  • maven org.bytedecoversion unspecified
  • maven org.bytedeco:javacv< 1.5.14

How to fix CVE-2026-102834

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-102834. EPSS is 0.34%. Act only if a listed version of JavaCV: Integer Overflow in is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.5.14, < 1.5.14. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-190: Integer Overflow. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 16, 2026 · GitHub Advisory Database

    Detected

    ### Summary parses the 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 , as documented in the class itself) - can supply a value in the range - . This drives the internal buf

  2. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    org.bytedeco:javacv fixed in 1.5.14

  3. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    org.bytedeco:javacv fixed in 1.5.14

  4. Oct 16, 2026 · GitHub Advisory Database

    Updated

    ### Summary parses the 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 , as documented in the class itself) - can supply a value in the range - . This drives the internal buf

Sources

  • CVE.orgVulnerability recordCVE-2026-102834

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-102834

    30-day exploitation probability 0.3%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-rxjv-24xq-76wc

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-102834

    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

    advisories.gitlab.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-rxjv-24xq-76wc

    JavaCV: Integer Overflow in IPCameraFrameGrabber Causes Infinite-Loop DoS

    osv.dev

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.