In libavc there is a possible information disclosure due to uninitialized data.

published 2019-09-27 7y ago modified 2026-06-17 4mo ago also EUVD-2019-18711

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112326322

Is CVE-2019-9336 in your stack? 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-2019-9336 updated 2026-11-05 cvss 6.5

libavc: information disclosure due to uninitialized data (A-112326322)

Red Hat Enterprise Linux 5 libavc1394 Red Hat Enterprise Linux 6 libavc1394 Red Hat Enterprise Linux 7 libavc1394 Red Hat Enterprise Linux 8 libavc1394
not affected: vulnerable code not present

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

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

CVSS scores

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

Affected products

n/a Android

Classification

Weakness

CWE-908 Use of Uninitialized Resource

References

source.android.com /security/bulletin/android-10
vendor-advisory

Sources

CVE List CVE-2019-9336
NVD CVE-2019-9336

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.