Skip to main content

JavaCV CVE-2026-102834

| EUVDEUVD-2026-103157 HIGH
Integer Overflow or Wraparound (CWE-190)
2026-10-16 GitHub_M GHSA-rxjv-24xq-76wc
7.5
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Control or MITM camera MJPEG endpoint
  2. Delivery
    Return oversized Content-Length header (>1073741824)
  3. Exploit
    Overflow 32-bit buffer-doubling loop
  4. Execution
    Grab thread spins at 100% CPU forever
  5. Impact
    Denial of service on application

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The affected application must use JavaCV's IPCameraFrameGrabber to consume a multipart MJPEG HTTP stream, and the Content-Length header in that stream must be attacker-influenced. This requires either (a) the application pointing at a malicious or compromised IP camera endpoint, or (b) a network attacker able to tamper with the plaintext HTTP response (these feeds are conventionally served over http://, enabling on-path injection). The trigger value is a parsed Content-Length in the range 1073741825-2147483647, which forces the signed-int buffer-doubling loop to overflow. Limiting factors: it only affects deployments that actually use IPCameraFrameGrabber (not JavaCV's other grabbers), the attacker must control or intercept the stream source, and impact is confined to availability (the frame-grabbing thread hangs) - no code execution or data exposure. Deployments using trusted cameras over authenticated/encrypted channels are not practically exposed.

Impact

This is a genuine but bounded risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) with base score 7.5 reflects a network-reachable, unauthenticated, no-interaction flaw whose sole impact is availability (C:N/I:N/A:H, CWE-190 integer overflow leading to an unbreakable CPU-spinning loop). There is no EPSS score, KEV listing, or public POC provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation - this is a high-CVSS issue driven entirely by the availability impact, not by observed attacker interest. A key limiting signal that the raw score hides: exploitation is not opportunistic against arbitrary internet targets. The victim application must actively consume an MJPEG stream from an endpoint the attacker controls (a malicious/compromised IP camera) or the attacker must sit on-path to tamper with the conventionally plaintext http:// stream. The AV:N/AC:L rating assumes the attacker already controls the camera source; for the pure man-in-the-middle variant, real-world complexity is higher than AC:L implies - treat the network-vector rating as a best case for an attacker who owns or has intercepted the stream source. Net: a real, worth-patching DoS for anyone running JavaCV's IPCameraFrameGrabber against untrusted or network-exposed camera endpoints, but lower urgency than the 7.5 suggests for deployments using only trusted, authenticated camera sources.

Exploit ScenarioDerived

An application uses JavaCV's IPCameraFrameGrabber to pull an MJPEG feed from an IP camera. An attacker who controls that camera endpoint - or who can tamper with the plaintext HTTP stream in transit - returns a multipart response whose Content-Length header is set between 1073741825 and 2147483647. When readImage() passes this value to ensureBufferCapacity(), the repeated 32-bit buffer doubling overflows to 0 and the grow loop never exits, trapping the grab() thread at 100% CPU with no timeout or interrupt path. No public exploit code is referenced, but the mechanism is fully detailed in the GHSA advisory with source snippets.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Denial of service in JavaCV's IPCameraFrameGrabber affects all versions prior to 1.5.14, where an attacker-influenced MJPEG stream can supply an oversized Content-Length header that overflows a 32-bit buffer-doubling loop and traps the frame-grabbing thread in a permanent 100% CPU spin. Unauthenticated remote attackers can trigger this either by operating a malicious or compromised IP camera endpoint the application connects to, or by tampering with the plaintext HTTP response in transit; the CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) confirms no privileges or user interaction are required and that impact is limited to availability. No public exploit code was identified at time of analysis and there is no CISA KEV listing, and the vendor has released a fixed version (1.5.14).

RemediationAI

Upgrade org.bytedeco:javacv to 1.5.14 or later; this release enforces a MAX_CONTENT_LENGTH bound of 64 MB on the parsed Content-Length, rejects values that are zero/negative or exceed that limit with an IOException, and rewrites the buffer-growth loop to use 64-bit long arithmetic so a large-but-valid frame can no longer wrap a signed int. The exact change is commit cd1977800b827beadf3c53c4032e57172845e0b4 (https://github.com/bytedeco/javacv/commit/cd1977800b827beadf3c53c4032e57172845e0b4) and the release is at https://github.com/bytedeco/javacv/releases/tag/1.5.14; the advisory is https://github.com/bytedeco/javacv/security/advisories/GHSA-rxjv-24xq-76wc. If immediate upgrade is not possible, restrict IPCameraFrameGrabber to trusted camera endpoints that are not reachable by untrusted parties and carry the MJPEG feed over an authenticated, encrypted channel (HTTPS/VPN or a private management VLAN), which removes the on-path tampering vector but does nothing against a compromised camera itself. Because the loop has no interrupt or timeout path, wrapping grab() calls in a bounded executor and force-cancelling the worker, or running the grabber in a separate JVM/container with CPU quotas, will contain the blast radius should a hostile stream be delivered, at the cost of losing the frame data from that stream. Disabling or replacing IPCameraFrameGrabber for untrusted sources is the only complete workaround short of patching.

Affected VersionsENISA

javacv < 1.5.14

Affected Packages

maven org.bytedeco:javacv fix: 1.5.14
euvd javacv fix: 1.5.14

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a CWE-190 integer overflow in JavaCV's Java interface to OpenCV/FFmpeg multimedia tooling. The affected class, IPCameraFrameGrabber, parses multipart MJPEG HTTP streams: readImage() locates the 'content-length: ' header, parses its value verbatim into a signed 32-bit int, and passes it to ensureBufferCapacity(int). That routine starts at the current buffer size (1024 bytes) and repeatedly doubles the capacity with an unchecked int multiplication until it is >= the desired capacity. A Content-Length in the range 1073741825-2147483647 drives capacity past Integer.MAX_VALUE, wrapping it to zero and causing the doubling loop's exit condition to never be satisfied again - a genuine infinite loop rather than a simple allocation failure. Because the code is single-threaded and offers no timeout or interrupt path, the calling thread spins indefinitely at 100% CPU, hanging grab()/grabBufferedImage(). The vulnerability is reachable only through this specific grabber consuming an MJPEG response; JavaCV's other grabbers are unaffected, and the impact is strictly availability with no memory corruption, code execution, or data exposure.

Know when Javacv gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 7.5 HIGH

Attacker controlling the camera source reaches the parser remotely with no auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is availability-only DoS, so C:N/I:N/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Oct 16, 2026 - 21:03 EUVD
CVE Published
Oct 16, 2026 - 19:51 cve.org
HIGH 7.5

DescriptionCVE.org

JavaCV provides Java interfaces to OpenCV, FFmpeg, and other multimedia libraries. Prior to 1.5.14, IPCameraFrameGrabber doubles a 32-bit buffer capacity without checking for overflow or bounding the parsed Content-Length. An application consumes an MJPEG response from a malicious camera endpoint or a tampered plaintext stream. The source can return an oversized Content-Length header in an MJPEG stream. Successful exploitation can trap the frame-grabbing thread in a permanent CPU-spinning loop and deny service. This issue is fixed in version 1.5.14.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 29 maven packages depend on org.bytedeco:javacv (3 direct, 26 indirect)

Ecosystem-wide dependent count for version 1.5.14.

Technical POC Analysis

CWE-190 (Integer Overflow or Wraparound) in IPCameraFrameGrabber.readImage() and its helper ensureBufferCapacity(int), both in src/main/java/org/bytedeco/javacv/IPCameraFrameGrabber.java.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

JavaCV's IPCameraFrameGrabber component, used in applications that process MJPEG streams from IP cameras, is affected by a high-severity denial-of-service vulnerability (CVE-2026-102834) that can cause a persistent CPU exhaustion condition, effectively halting video frame processing. This flaw can be triggered by an unauthenticated remote actor who either operates a malicious or compromised camera endpoint or intercepts and modifies unencrypted HTTP traffic, potentially disrupting physical security monitoring and surveillance operations. Leadership should prioritize patching to version 1.5.14 to restore availability and prevent operational blind spots.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

Prevalence
Medium
popular Java multimedia library, but IP-camera grabber is a niche component
Threat Intel
1
1 source
Social Media
2
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy