CVE-2026-53200

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX

XN has already been extracted from its bitfield position so using FIELD_PREP() on the mask that clears XN[0] is completely broken, having the effect of unconditionally granting execute permissions...

Fix the obvious mistake by manipulating the right bit.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
2.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b95976c2ea446044553a5f469c0bae13553d75ab
generic

KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49b32ddb87a3a109afecea89e55d70f73956b8bc

Vendor Advisories for CVE-2026-53200(1)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 51× 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-06 16:52 UTCEG score recompute
  2. 2026-07-06 16:52 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 03:57 UTCEG score recompute
  6. 2026-07-06 03:57 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 15:03 UTCEG score recompute
  10. 2026-07-05 15:03 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 02:08 UTCEG score recompute
  14. 2026-07-05 02:08 UTCGHSA enrichment
  15. 2026-07-04 13:13 UTCEG score recompute
  16. 2026-07-04 13:13 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 00:19 UTCEG score recompute
  20. 2026-07-04 00:19 UTCGHSA enrichment
  21. 2026-07-03 11:25 UTCEG score recompute
  22. 2026-07-03 11:25 UTCGHSA enrichment
  23. 2026-07-02 22:24 UTCEG score recompute
  24. 2026-07-02 22:24 UTCGHSA enrichment
  25. 2026-07-02 09:29 UTCEG score recompute
Show 26 more
  1. 2026-07-02 09:29 UTCGHSA enrichment
  2. 2026-07-01 20:35 UTCEG score recompute
  3. 2026-07-01 20:35 UTCGHSA enrichment
  4. 2026-07-01 07:41 UTCEG score recompute
  5. 2026-07-01 07:41 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 18:47 UTCEG score recompute
  8. 2026-06-30 18:47 UTCGHSA enrichment
  9. 2026-06-30 05:53 UTCEG score recompute
  10. 2026-06-30 05:53 UTCGHSA enrichment
  11. 2026-06-29 16:59 UTCEG score recompute
  12. 2026-06-29 16:58 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 04:02 UTCEG score recompute
  16. 2026-06-29 04:02 UTCGHSA enrichment
  17. 2026-06-28 15:07 UTCEG score recompute▲ 8.80
  18. 2026-06-28 15:07 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 10:07 UTCEG score recompute
  26. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53200?
CVE-2026-53200 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX XN has already been extracted from its bitfield position so using FIELD_PREP() on the mask that clears XN[0] is completely broken, having the effect of unconditionally granting…
When was CVE-2026-53200 disclosed?
CVE-2026-53200 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53200 actively exploited?
CVE-2026-53200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53200?
CVE-2026-53200 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53200?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53200, 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-53200

Explore →

Is Your Infrastructure Affected by CVE-2026-53200?

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

Start Free Scan →Browse All CVEs