CVE-2026-52920

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

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

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

netfilter: xt_policy: fix strict mode inbound policy matching

match_policy_in() walks sec_path entries from the last transform to the first one, but strict policy matching needs to consume info->pol[] in the same forward order as the rule layout.

Derive the strict-match policy position from the number of transforms already consumed so that multi-element inbound rules are matched consistently.

CVSS v3
8.3
EG Score
8.3(high)
EPSS
21.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

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

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/938867e870fb5471bb16f442aeac81326e05bf65
generic

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82664d0f1ba25e4f9a71994954abae24c60f4067
generic

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b2b4d7d4e203c92db8966b163edfacb1f0e1e29
generic

netfilter: xt_policy: fix strict mode inbound policy matching - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/392cc1d8408b5665215c1e9290bbf0f92339b043

Vendor Advisories for CVE-2026-52920(2)

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 38× 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-07 02:53 UTCEG score recompute
  2. 2026-07-07 02:53 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:46 UTCEG score recompute
  6. 2026-07-06 15:46 UTCGHSA enrichment
  7. 2026-07-06 04:36 UTCEG score recompute
  8. 2026-07-06 04:36 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:19 UTCEG score recompute
  12. 2026-07-05 17:18 UTCGHSA enrichment
  13. 2026-07-05 06:09 UTCEG score recompute
  14. 2026-07-05 06:09 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 18:57 UTCEG score recompute
  17. 2026-07-04 18:57 UTCGHSA enrichment
  18. 2026-07-04 07:48 UTCEG score recompute
  19. 2026-07-04 07:48 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 20:40 UTCEG score recompute
  22. 2026-07-03 20:40 UTCGHSA enrichment
  23. 2026-07-03 09:32 UTCEG score recompute
  24. 2026-07-03 09:32 UTCGHSA enrichment
  25. 2026-07-02 22:24 UTCEG score recompute
Show 26 more
  1. 2026-07-02 22:24 UTCGHSA enrichment
  2. 2026-07-02 11:16 UTCEG score recompute
  3. 2026-07-02 11:16 UTCGHSA enrichment
  4. 2026-07-02 00:07 UTCEG score recompute
  5. 2026-07-02 00:07 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 12:59 UTCEG score recompute
  8. 2026-07-01 12:59 UTCGHSA enrichment
  9. 2026-07-01 01:52 UTCEG score recompute
  10. 2026-07-01 01:52 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 14:44 UTCEG score recompute▲ 8.30
  13. 2026-06-30 14:44 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.3 · severity → HIGH
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 11:42 UTCEG score recompute
  21. 2026-06-27 11:42 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-24 08:42 UTCEG score recompute
  26. 2026-06-24 08:40 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52920?
CVE-2026-52920 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: xt_policy: fix strict mode inbound policy matching matchpolicyin() walks sec_path entries from the last transform to the first one, but strict policy matching needs to consume info->pol[] in the same forward order as the…
When was CVE-2026-52920 disclosed?
CVE-2026-52920 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52920 actively exploited?
CVE-2026-52920 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52920?
CVE-2026-52920 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-52920?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52920, 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-52920

Explore →

Is Your Infrastructure Affected by CVE-2026-52920?

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

Start Free Scan →Browse All CVEs