CVE-2026-49299

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

In OpenStack Neutron before 28.0.1, the tagging controller enforces plural policy action names on single-tag write operations while the defined policy rules use singular names. The mismatched names evaluate as allowed under the default policy, permitting a project reader to create and update tags on same-project resources. Deployments running Neutron 26.0.0 or later are affected.

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

Published

May 28, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated May 29, 2026
No patch confirmed yet.
generic

oss-security - [OSSA-2026-016] OpenStack Neutron: Tagging policy bypass allows project readers to mutate tags (CVE-2026-pending)

https://www.openwall.com/lists/oss-security/2026/05/28/8
generic
https://review.opendev.org/c/openstack/neutron/+/989099
generic

Bug #2150132 “[OSSA-2026-016] Neutron tagging single-tag create ...” : Bugs : neutron

https://bugs.launchpad.net/bugs/2150132

Vendor Advisories for CVE-2026-49299(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
neutron2:17.1.1-6 ... 2:28.0.1-2 (91 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
neutron2:21.0.0-7 ... 2:28.0.1-2 (61 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
neutron2:26.0.0-92:26.0.0-9+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
neutron2:26.0.0-9 ... 2:28.0.0~rc2-2 (17 versions)2:28.0.0-4—
PyPI(1)
PackageVulnerable rangeFixed inDependents
neutron26.0.0 ... 28.0.0 (8 versions)28.0.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 39× 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 161 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-49299?
CVE-2026-49299 is a medium vulnerability published on May 28, 2026. In OpenStack Neutron before 28.0.1, the tagging controller enforces plural policy action names on single-tag write operations while the defined policy rules use singular names. The mismatched names evaluate as allowed under the default policy, permitting a project reader to create and update tags…
When was CVE-2026-49299 disclosed?
CVE-2026-49299 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49299 actively exploited?
CVE-2026-49299 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 78.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49299?
CVE-2026-49299 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-49299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49299, 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-49299

Explore →

Is Your Infrastructure Affected by CVE-2026-49299?

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

Start Free Scan →Browse All CVEs