CVE-2026-49299: In OpenStack Neutron before 28.0.1, the tagging controller enforces plural policy action names on single-ta...
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.
Security readout for executives and security teams
This flaw lets a low-privileged OpenStack project reader change tags on resources within the same project. It does not show direct system takeover, but tag changes can affect operations if tags drive automation, inventory, billing, or governance decisions. OpenStack deployments running Neutron 26.0.0 or later before 28.0.1 are affected. Exposure depends on whether project reader accounts can reach the Neutron API and whether resource tags influence operational workflows. Treat as a moderate-priority cloud control issue. Patch on the normal security maintenance track, faster where tags feed automated decisions or compliance reporting. Mitigation focus: Upgrade Neutron to 28.0.1 or a vendor-supported fixed release.; Review OpenStack vendor advisories for backported fixes.; Assess whether tags control automation, inventory, billing, or policy decisions..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.