Bug 2507588 (CVE-2026-55707) - CVE-2026-55707 openstack-neutron: CVE-2026-55707 openstack-neutron: Shared-network consumer can re-scope another project's subnets via subnetpool onboarding
Summary: CVE-2026-55707 openstack-neutron: CVE-2026-55707 openstack-neutron: Shared-ne...
Keywords:
Status: NEW
Alias: CVE-2026-55707
Deadline: 2026-07-29
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-27 17:34 UTC by OSIDB Bzimport
Modified: 2026-07-29 15:20 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-27 17:34:45 UTC
*** This is a vulnerability report sent to us through https://issues.redhat.com/browse/PSIRTSUPT-20145 and was created using the PoC auto-triage agents. It contains hints on the vulnerability extracted by the IA and the full report. ALWAYS review it before any action. Once working on this, don't forget to also update the JSM ticket. ***

An authorization bypass was found in the OpenStack Neutron subnetpool onboarding API endpoint (PUT /v2.0/subnetpools/{id}/onboard_network_subnets). When a caller supplies a network_id, the API only verifies that the network is visible to the caller but does not verify that the caller owns the subnets on that network. When a network is RBAC-shared or globally shared, any project member with network visibility can invoke the API to onboard another project's subnets into the caller's own subnetpool, mutating the victim's subnet records (setting subnetpool_id to the attacker-controlled pool). If the attacker's subnetpool is associated with an address scope, Neutron syncs the victim's router interfaces with the attacker-controlled address scope, silently altering L3 routing, NAT, and address-scope behavior. The upstream fix adds an ownership check ensuring the caller has admin-or-owner authority over each subnet being onboarded, not merely visibility of the parent network.


Note You need to log in before you can comment on or make changes to this bug.