CVE-2026-33542

MEDIUMNVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Incus is a system container and virtual machine manager. Prior to version 6.23.0, a lack of validation of the image fingerprint when downloading from simplestreams image servers opens the door to image cache poisoning and under very narrow circumstances exposes other tenants to running attacker controlled images rather than the expected one. Version 6.23.0 patches the issue.

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Incus does not verify combined fingerprint when downloading images from simplestreams servers · Advisory · lxc/incus · GitHub

https://github.com/lxc/incus/security/advisories/GHSA-p8mm-23gg-jc9r

Vendor Advisories for CVE-2026-33542(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(7 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/lxc/incus———
github.com/lxc/incus/v6—6.23.0—
github.com/lxc/incus/v6/client—6.23.0—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.4-2+deb13u4~bpo12+1 (9 versions)6.0.4-2+deb13u5—
lxd5.0.2+git20231211.1364ae4-9, 5.0.2+git20231211.1364ae4-9+deb13u1, 5.0.2+git20231211.1364ae4-9+deb13u2, 5.0.2+git20231211.1364ae4-9+deb13u35.0.2+git20231211.1364ae4-9+deb13u4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lxd5.0.2-5, 5.0.2-5+deb12u1, 5.0.2-5+deb12u2, 5.0.2-5+deb12u35.0.2-5+deb12u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.6-1 (11 versions)6.0.6-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-02 13:14 UTCOSV refresh
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 46 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:17 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 10:04 UTCEG score recompute
  12. 2026-08-16 10:04 UTCVendor advisory
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 06:22 UTCEG score recompute
  16. 2026-08-14 06:22 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 20:39 UTCEG score recompute
  19. 2026-08-12 20:39 UTCVendor advisory
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 04:13 UTCEG score recompute
  22. 2026-08-11 04:13 UTCVendor advisory
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 05:06 UTCEG score recompute
  25. 2026-08-10 05:06 UTCVendor advisory
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 05:55 UTCEG score recompute
  28. 2026-08-09 05:55 UTCVendor advisory
  29. 2026-08-07 16:21 UTCEG score recompute
  30. 2026-08-06 13:46 UTCEPSS rescore
  31. 2026-08-06 00:49 UTCEG score recompute
  32. 2026-08-06 00:49 UTCVendor advisory
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 10:38 UTCEPSS rescore
  36. 2026-08-03 23:13 UTCEG score recompute
  37. 2026-08-03 23:13 UTCVendor advisory
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-02 15:14 UTCEG score recompute▼ 0.90
  40. 2026-08-02 15:14 UTCVendor advisory
  41. 2026-08-02 02:27 UTCEPSS rescore
  42. 2026-07-30 16:28 UTCEPSS rescore
  43. 2026-07-30 01:30 UTCEPSS rescore
  44. 2026-07-27 14:13 UTCEPSS rescore
  45. 2026-07-27 12:50 UTCEG score recompute
  46. 2026-07-27 12:50 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33542?
CVE-2026-33542 is a medium vulnerability published on March 26, 2026. Incus is a system container and virtual machine manager. Prior to version 6.23.0, a lack of validation of the image fingerprint when downloading from simplestreams image servers opens the door to image cache poisoning and under very narrow circumstances exposes other tenants to running attacker…
When was CVE-2026-33542 disclosed?
CVE-2026-33542 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33542 actively exploited?
CVE-2026-33542 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.2% of all scored CVEs.
What is the CVSS score of CVE-2026-33542?
CVE-2026-33542 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-33542?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33542, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33542

Explore →

Is Your Infrastructure Affected by CVE-2026-33542?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs