CVE-2026-32187

✕ Withdrawn — historical dataUNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed: 0

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

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

CVSS v3
—
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

March 27, 2026

Last Modified

April 15, 2026

Vendor Advisories for CVE-2026-32187(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 0× 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-08-14 19:26 UTCVendor advisory
  2. 2026-08-14 19:26 UTCGHSA enrichment
  3. 2026-08-12 00:45 UTCVendor advisory
  4. 2026-08-12 00:45 UTCGHSA enrichment
  5. 2026-08-09 05:49 UTCGHSA enrichment
  6. 2026-08-06 00:45 UTCVendor advisory
  7. 2026-08-06 00:45 UTCGHSA enrichment
  8. 2026-08-02 15:09 UTCEG score recompute
  9. 2026-08-02 15:09 UTCVendor advisory
  10. 2026-08-02 15:09 UTCGHSA enrichment
  11. 2026-07-23 03:08 UTCEG score recompute▼ 4.20
  12. 2026-06-11 23:00 UTCVendor advisory
  13. 2026-06-11 23:00 UTCGHSA enrichment
  14. 2026-06-10 17:46 UTCVendor advisory
  15. 2026-06-10 17:46 UTCGHSA enrichment
  16. 2026-06-09 15:52 UTCVendor advisory
  17. 2026-06-09 15:52 UTCGHSA enrichment
  18. 2026-06-08 13:59 UTCVendor advisory
  19. 2026-06-08 13:59 UTCGHSA enrichment
  20. 2026-06-07 11:53 UTCVendor advisory
  21. 2026-06-07 11:53 UTCGHSA enrichment
  22. 2026-05-20 20:02 UTCEG score recompute
  23. 2026-05-20 20:02 UTCVendor advisory
  24. 2026-05-20 20:02 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(3)

What is CVE-2026-32187?
CVE-2026-32187 is a publicly disclosed vulnerability published on March 27, 2026. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
When was CVE-2026-32187 disclosed?
CVE-2026-32187 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-32187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32187, 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

Explore the affected products and dependency analysis for CVE-2026-32187

Explore →

Is Your Infrastructure Affected by CVE-2026-32187?

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

Book a Demo →Browse All CVEs