CVE-2026-45886

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

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

bpf: Fix bpf_xdp_store_bytes proto for read-only arg

While making some maps in Cilium read-only from the BPF side, we noticed that the bpf_xdp_store_bytes proto is incorrect. In particular, the verifier was throwing the following error:

; ret = ctx_store_bytes(ctx, l3_off + offsetof(struct iphdr, saddr), &nat->address, 4, 0); 635: (79) r1 = *(u64 *)(r10 -144) ; R1=ctx() R10=fp0 fp-144=ctx() 636: (b4) w2 = 26 ; R2=26 637: (b4) w4 = 4 ; R4=4 638: (b4) w5 = 0 ; R5=0 639: (85) call bpf_xdp_store_bytes#190 write into map forbidden, value_size=6 off=0 size=4

nat comes from a BPF_F_RDONLY_PROG map, so R3 is a PTR_TO_MAP_VALUE. The verifier checks the helper's memory access to R3 in check_mem_size_reg, as it reaches ARG_CONST_SIZE argument. The third argument has expected type ARG_PTR_TO_UNINIT_MEM, which includes the MEM_WRITE flag. The verifier thus checks for a BPF_WRITE access on R3. Given R3 points to a read-only map, the check fails.

Conversely, ARG_PTR_TO_UNINIT_MEM can also lead to the helper reading from uninitialized memory.

This patch simply fixes the expected argument type to match that of bpf_skb_store_bytes.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (6)

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

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6557f1565d779851c4db9c488c49c05a47a6e72f
generic

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57f7f6a0ad04a65c8a7a067b2f56cbbf2aec9e52
generic

bpf: Fix bpf_xdp_store_bytes proto for read-only arg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0db169a91381a473b7974021d1c02f8da72c5775

Vendor Advisories for CVE-2026-45886(1)

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

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

Weakness Classification(1)

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

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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.

Showing the most recent 100 of 201 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 09:08 UTCEG score recompute
  6. 2026-09-14 09:08 UTCVendor advisory
  7. 2026-09-14 09:08 UTCGHSA enrichment
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-13 04:09 UTCOSV refresh
  10. 2026-09-12 15:01 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-10 09:34 UTCEPSS rescore
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 05:48 UTCEG score recompute
  2. 2026-08-25 05:48 UTCVendor advisory
  3. 2026-08-25 05:47 UTCGHSA enrichment
  4. 2026-08-23 15:35 UTCEG score recompute
  5. 2026-08-23 15:35 UTCVendor advisory
  6. 2026-08-23 15:34 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 20:54 UTCVendor advisory
  9. 2026-08-21 20:54 UTCGHSA enrichment
  10. 2026-08-20 17:42 UTCEG score recompute
  11. 2026-08-20 17:42 UTCVendor advisory
  12. 2026-08-20 17:42 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:21 UTCEG score recompute
  17. 2026-08-17 09:21 UTCVendor advisory
  18. 2026-08-17 09:21 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:55 UTCEG score recompute
  21. 2026-08-16 02:55 UTCVendor advisory
  22. 2026-08-16 02:55 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 04:05 UTCEG score recompute
  26. 2026-08-14 04:05 UTCVendor advisory
  27. 2026-08-14 04:05 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-13 03:11 UTCEG score recompute
  30. 2026-08-13 03:11 UTCVendor advisory
  31. 2026-08-13 03:11 UTCGHSA enrichment
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-12 02:18 UTCVendor advisory
  34. 2026-08-12 02:18 UTCGHSA enrichment
  35. 2026-08-11 01:24 UTCEG score recompute
  36. 2026-08-11 01:24 UTCVendor advisory
  37. 2026-08-11 01:24 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 00:30 UTCEG score recompute
  40. 2026-08-10 00:30 UTCVendor advisory
  41. 2026-08-10 00:30 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-08 23:37 UTCEG score recompute
  44. 2026-08-08 23:37 UTCVendor advisory
  45. 2026-08-08 23:37 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 22:43 UTCEG score recompute
  48. 2026-08-07 22:43 UTCVendor advisory
  49. 2026-08-07 22:43 UTCGHSA enrichment
  50. 2026-08-06 21:50 UTCEG score recompute
  51. 2026-08-06 21:50 UTCVendor advisory
  52. 2026-08-06 21:50 UTCGHSA enrichment
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-05 20:56 UTCEG score recompute
  55. 2026-08-05 20:56 UTCVendor advisory
  56. 2026-08-05 20:56 UTCGHSA enrichment
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:39 UTCEPSS rescore
  60. 2026-08-03 18:44 UTCEG score recompute
  61. 2026-08-03 18:44 UTCVendor advisory
  62. 2026-08-03 18:44 UTCGHSA enrichment
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-02 16:38 UTCEG score recompute
  65. 2026-08-02 16:38 UTCVendor advisory
  66. 2026-08-02 16:38 UTCGHSA enrichment
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 15:45 UTCEG score recompute
  69. 2026-08-01 15:45 UTCVendor advisory
  70. 2026-08-01 15:45 UTCGHSA enrichment
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-31 08:04 UTCEG score recompute
  73. 2026-07-31 08:04 UTCGHSA enrichment
  74. 2026-07-30 16:28 UTCEPSS rescore
  75. 2026-07-30 01:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45886?
CVE-2026-45886 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix bpfxdpstore_bytes proto for read-only arg While making some maps in Cilium read-only from the BPF side, we noticed that the bpfxdpstore_bytes proto is incorrect. In particular, the verifier was throwing the following…
When was CVE-2026-45886 disclosed?
CVE-2026-45886 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45886 actively exploited?
CVE-2026-45886 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-45886?
CVE-2026-45886 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45886?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45886, 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-45886

Explore →

Is Your Infrastructure Affected by CVE-2026-45886?

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