Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-63338high8.3

IXP Manager has Broken Object-Level Authorization

Impact

IXP Manager, a web application for managing Internet Exchange Points, has a broken object-level authorization weakness. Affected versions are prior to 7.3.0, where an authenticated user can view and edit another user's resources without authorization. The issue is due to the API-key edit/update path not checking the user ID.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

inex · GitHub_M

IXP-Manager

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 7.3.0

unaffected

unknown

Other versions: unknown

Original source description

IXP Manager is a full-stack web application for managing Internet Exchange Points. Prior to version 7.3.0, an authenticated user can view and edit a resource belonging to another user without authorization. The API-key edit/update path in ApiKeyController selects records by identifier without checking that user_id matches the caller, allowing access to another user's API-key record. This issue is fixed in version 7.3.0.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-63338

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-863 ↗

CWE-863: Incorrect Authorization

GitHub_M

Related →
CWE-639 ↗

CWE-639: Authorization Bypass Through User-Controlled Key

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

3 sources