CVE-2026-65458

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-23. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

Contributor Sensitive Data Exposure in Polylang <= 3.8.5 versions.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 23, 2026

References (1)

Vendor Advisories for CVE-2026-65458(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 15× in last 7d / 15× 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-07-28 02:29 UTCEG score recompute
  2. 2026-07-28 02:29 UTCGHSA enrichment
  3. 2026-07-27 14:14 UTCEPSS rescore
  4. 2026-07-27 02:49 UTCEG score recompute
  5. 2026-07-27 02:49 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 03:12 UTCEG score recompute
  9. 2026-07-26 03:12 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 11:44 UTCEG score recompute
  15. 2026-07-23 11:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65458?
CVE-2026-65458 is a medium vulnerability published on July 23, 2026. Contributor Sensitive Data Exposure in Polylang <= 3.8.5 versions.
When was CVE-2026-65458 disclosed?
CVE-2026-65458 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65458 actively exploited?
CVE-2026-65458 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 88.0% of all scored CVEs.
What is the CVSS score of CVE-2026-65458?
CVE-2026-65458 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-65458?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65458, 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-65458

Explore →

Is Your Infrastructure Affected by CVE-2026-65458?

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

Start Free Scan →Browse All CVEs