Install each product's own fix now. Restricting who can reach System REST APIs does not replace it. Research: primary sources retrieved November 11, 2026.
Check these three things.
System owner: confirm API Manager 4.5.0 subscriptions have U2 update level 32 or higher.Which level applies
Subscription fixes are that base version's U2 level or higher, through WSO2 Updates.
U2 means Update 2.0, the update level on the installed base version.
The base version is the three-part number, such as 4.5.0. API Manager 4.5.0 at update level 32 is 4.5.0.32.
Update level 32 applies to the API Manager 4.5.0 subscription row only. It is not a universal release.
On API Manager 4.5.0, the control plane, gateway, and traffic manager can be updated separately. A fix on one does not fix the others.
The subscription FAQ describes the update channel. Use the advisory for this CVE's rows.
All fifteen subscription rows: U2 level or higher for that base version
Product
Base version
Update level or higher
WSO2 API Control Plane
4.5.0
33
WSO2 API Manager
4.5.0
32
WSO2 API Manager
4.4.0
49
WSO2 API Manager
4.3.0
85
WSO2 API Manager
4.2.0
173
WSO2 API Manager
4.1.0
233
WSO2 API Manager
4.0.0
370
WSO2 API Manager
3.2.1
70
WSO2 API Manager
3.2.0
450
WSO2 API Manager
3.1.0
347
WSO2 Identity Server as Key Manager
5.10.0
367
WSO2 Open Banking AM
2.0.0
396
WSO2 Open Banking IAM
2.0.0
416
WSO2 Traffic Manager
4.5.0
31
WSO2 Universal Gateway
4.5.0
31
Community builds use the public fix linked from the advisory.
If that public fix cannot be applied, migrate to the latest unaffected version of the same product.
No single replacement release is named.
Install the fix even when System REST APIs are already restricted.
A finished update still leaves earlier use to the harm review.
Ranges before the first listed base version are unknown. Unknown is not safe.
API Manager before 3.1.0.
Identity Server as Key Manager before 5.10.0.
Open Banking AM before 2.0.0.
Open Banking IAM before 2.0.0.
API Control Plane before 4.5.0.
Universal Gateway before 4.5.0.
Traffic Manager before 4.5.0.
The CVE record's default for each listed product is unaffected, and the older ranges are marked unknown. That default does not make an unknown older range safe.
The CVE record names two internal packages with default status unknown. Do not derive a package version from a product update level.
WSO2 Carbon API Manager Rest API Utility, package org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.util.
WSO2 Carbon API Manager Rest API Common Functions, package org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.common.
Record these fields.
Installed product.
Base version.
Update level.
Subscription or community channel.
Source of the record.
Date checked.
Network owner: confirm access to the affected WSO2 management APIs; the sign-in requirement remains unresolved.When the risk applies
The affected surface is this product's System REST APIs, the management interfaces used for administrative actions.
APIs created and exposed through the WSO2 API Manager API Gateway are outside this flaw.
That exclusion does not clear Universal Gateway. Universal Gateway 4.5.0 below update level 31 stays on its own row.
API Manager 4.5.0 can deploy the control plane, gateway, and traffic manager separately.
The 4.5.0 architecture page says "the control plane does not process API requests or execute API logic."
That role does not remove API Control Plane from its own row.
Who may call the System REST APIs is unresolved.
The advisory says "a user with low privileges".
The CVE description says "users with lower privilege roles".
The published score says privileges required are none.
A low-privilege user would mean a signed-in user.
Privileges required none would mean no sign-in is required.
Neither reading is verified.
The score rates the flaw over the network. It does not map your network.
If nobody can reach the System REST APIs, record that limit. The product can need the fix even then.
Record these fields.
Product.
Where the System REST APIs are reached.
Who can call them.
Whether APIs created and exposed through the API Gateway were kept out of this check.
Source of the record.
Date checked.
Security owner: review existing audit and change records for unexplained administrative actions, including products already updated, and start response if one appears.What the records can show
Start response when an administrative action should not have been taken, even if this CVE is not established as the cause.
Review the period the affected version was in use, including products already updated. A later fix does not settle earlier changes.
The advisory date and the CVE date are different events.
WSO2 published advisory WSO2-2025-4733, version 1.0.0, on January 26, 2026.
The CVE record was published on November 2, 2026.
Affected use can also predate the advisory.
Preserve existing records before an update when they still exist.
For API Manager 4.5.0, audit logs are enabled by default.
The documented file is audit.log under API-M_HOME/repository/logs.
They trace user activity and changes.
They do not list an indicator for this CVE.
They do not promise every unauthorized action was recorded.
Gateway API logs cover requests going through the WSO2 API Gateway.
They are off unless enabled per API.
They do not show whether System REST actions were recorded.
A clean log is not proof of no change.
A missing log leaves the question unresolved.
CISA's November 2, 2026 note says exploitation none. KEV catalog 2026.11.10 has no entry. Neither proves that attacks did not happen.
Record these fields.
Records reviewed.
Source of the records.
Period covered.
Date reviewed.
Do Now
System owner: update API Manager 4.5.0 subscriptions to U2 update level 32 or higher.Proof the update is done
Use the row for the installed product and base version.
API Manager 4.5.0 subscriptions need U2 update level 32 or higher.
Do not copy level 32 onto another row.
Subscription updates come through WSO2 Updates.
For a community build, apply the public fix linked from the advisory.
A version number alone does not confirm that fix.
If that public fix cannot be applied, migrate to the latest unaffected version of the same product.
No universal replacement release is named.
If the base version is in an unknown range, do not mark it fixed.
A finished update does not settle earlier changes.
Record these fields.
Installed product.
Base version.
Update level after the work.
Subscription or community path used.
Source of the record.
Date checked.
Network owner: limit this product's System REST APIs to trusted networks, as a reachability reduction that does not replace the fix.What to record
Limit the management System REST APIs to trusted networks.
This is a reachability reduction, not a vendor patch.
APIs created and exposed through the API Manager API Gateway are a different surface.
Universal Gateway can need its own fix.
The privilege needed to call System REST APIs remains unresolved.
If reach is already limited, record that evidence. The product can need the fix even then.
Record these fields.
Product.
Who can reach the System REST APIs.
Source of the record.
Date checked.
Security owner: review existing audit and change records for unexplained administrative actions, including products already updated, and start response if one appears.Where to look first
Preserve existing records before the update when you still can.
Review the period the product was reachable, including products already updated.
Include use before the January 26, 2026 advisory. The November 2, 2026 CVE date is a later publication.
For API Manager 4.5.0, start with audit.log under API-M_HOME/repository/logs.
Gateway API logs do not establish System REST history.
Start response even if this CVE is not established as the cause.
A later fix does not settle earlier changes.
A clean log is not proof of no change.
A missing log leaves the question unresolved.
Record these fields.
Records reviewed.
Source of the records.
Period covered.
Date reviewed.
Do Next
System owner: if a base version is unknown, or the community public fix cannot be applied, ask the provider which fix or unaffected version applies.What to ask
Ask which fix applies to each older unknown base version.
Ask which unaffected version of the same product applies when the linked community fix cannot be applied.
Do not invent a backport.
Do not invent a universal replacement release.
Do not treat an unknown package version as a product update level.