WaratekVRT Sign in

CVE-2026-102834

Severity7.5 High CVSS 3.1
Fixed in1.5.14
WeaknessInteger overflow (CWE-190)
Published16 Oct 2026
Updated28 Oct 2026

Published 29 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

Description

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.

Exploitation status

Proof of concept only

A proof of concept exists, but no reviewed exploit catalogue lists this CVE.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: poc CISA recorded that an exploit has been demonstrated. Automatable: yes, technical impact: partial.
  • Indexed PoC none indexed
  • EPSS 0.50% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: bytedeco/javacv cd19778.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/bytedeco/javacv/commit/cd1977800b827beadf3c53c4032e57172845e0b4 : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.bytedeco:javacv 0 1.5.14 unbounded

Products and versions

1 product, 1 version entry
SourceVendorProductSchemeAffected versions
osv org.bytedeco javacv generic < 1.5.14

References

URLTags
https://github.com/bytedeco/javacv/commit/cd1977800b827beadf3c53c4032e57172845e0b4 commit
https://github.com/bytedeco/javacv/security/advisories/GHSA-rxjv-24xq-76wc WEB
https://github.com/bytedeco/javacv PACKAGE
https://github.com/bytedeco/javacv/releases/tag/1.5.14 WEB

Timeline

Published2026-10-16By the CVE Program.
NVD record modified2026-10-28NVD's own last-modified date for this record.