major vulnerability· requires attention

Unauthenticated RCE in image library used broadly (libpng/Android). High CVSS, affects many apps and Android devices — widespread impact potential.

Applications

CVE-2026-58936

9.8

Critical

EPSS n/aPatch available

Unauthenticated RCE via use-after-free in png_set_tRNS (libpng/Android).

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

No EPSS score yet

Published 2 Nov 2026Analysed here 5 Nov 2026CVSS scored by CISA

common questions

Is CVE-2026-58936 being exploited?

Not confirmed. CVE-2026-58936 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-58936?

CVE-2026-58936 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58936?

Yes. A fix has been recorded for CVE-2026-58936. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58936 affect?

CVE-2026-58936 affects libpng (png_set_tRNS), Android devices (per Android security bulletin), Any application or server parsing PNG images. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58936?

Apply vendor/Android updates ASAP; update libpng; block/scan untrusted PNGs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

libpng (png_set_tRNS)Android devices (per Android security bulletin)Any application or server parsing PNG images

impact

Remote code execution by sending a crafted PNG to parsers, allowing arbitrary code execution without user interaction.

action required

Immediate action required

affected versions

Google Android

affected17
affected16-qpr2
affected16
affected15
affected14

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation: none
automatable: yes
technical impact: total

Assessed by CISA 4 Nov 2026 (SSVC 2.0.3).

timeline

2 Nov 2026Published
4 Nov 2026CISA SSVC assessment: exploitation none · 1 day later
4 Nov 2026CVE record last updated · same day later
5 Nov 2026Analysed by vulneraibility.com · 1 day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

1 reference in the CVE record: 1 link

Linksource.android.com /docs/security/bulletin/2026/2026-11-01

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free