Skip to content
Fencer Intel
medium 5.5

CVE-2018-5269 json

Reachable Assertion in OpenCV.

published 8y ago modified last mo. also GHSA-89rj-5ggj-3p9p , PYSEC-2026-2812 , PYSEC-2026-703 , EUVD-2021-2178

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

In OpenCV 3.3.1, an assertion failure happens in cv::RBaseStream::setPos in modules/imgcodecs/src/bitstrm.cpp because of an incorrect integer cast.

Patch / fix

  • pypi opencv-python 3.4.1.15
  • pypi opencv-contrib-python 3.4.1.15
  • opencv Debian 14, Debian 13, Debian 12 3.2.0+dfsg-6

debian advisories DEBIAN-CVE-2018-5269

  • opencv Ubuntu 16.04 LTS 2.4.9.1+dfsg-1.5ubuntu1.1
  • opencv Ubuntu 18.04 LTS 3.2.0+dfsg-4ubuntu0.1

ubuntu advisories UBUNTU-CVE-2018-5269

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-5269 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-5269 updated cvss 3.3

opencv: Assertion failure due to incorrect integer cast

  • Red Hat Enterprise Linux 6 opencv, opencv-python Red Hat Enterprise Linux 7 opencv, opencv-core, opencv-python Red Hat Enterprise Linux 8 opencv, opencv-core, opencv-contrib, python3-opencv
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.38% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/opencv/opencv/issues/10540 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
OSV 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi opencv-python
<3.4.1.15
3.4.1.15
pypi opencv-contrib-python
<3.4.1.15
3.4.1.15

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.