dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-12686

CRITICAL · 9.3 CVSS v4.0 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authenticated user could manipulate a company ID parameter in a POST request to the backend to gain unauthorised access to other companies hosted within the same subdomain environment. The application does not adequately verify whether the requested company ID belongs to the authenticated user’s session, resulting in a cross-tenant authorisation bypass. If this vulnerability is successfully exploited, it allows unauthorised access to sensitive customer information, including billing data, and may enable the unauthorised modification of third-party data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a cross-tenant authorization bypass vulnerability in a multi-tenant web application. An authenticated user can manipulate the company ID parameter in POST requests to access or modify data belonging to other companies hosted on the same subdomain. The application fails to verify that the requested company ID belongs to the authenticated user's session, allowing unauthorized access to sensitive customer information including billing data.

MitigationImplement proper authorization validation to ensure the requested company ID belongs to the authenticated user's session before processing any request. All company-specific operations must verify tenant context matches the authenticated user's tenant.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the application is multi-tenant
    Review application architecture documentation or examine POST request parameters for tenant/company identifiers such as company_id, tenant_id, org_id, or customer_id in HTTP traffic.
    Affected if The application uses a multi-tenant model where users belong to specific companies and process data within company-specific contexts.
  2. Locate company-specific POST endpoints
    Capture or review HTTP traffic using a proxy tool or server logs to identify POST requests that contain company ID, tenant ID, or organization ID parameters in the request body.
    Affected if POST requests accept and process a company/tenant identifier as a parameter.
  3. Test for authorization bypass
    Authenticate as a user in one company, then modify the company ID parameter in a POST request to a value belonging to a different company. Observe if the application returns data or performs actions for the alternate company.
    Affected if The application processes the request using the supplied company ID without verifying it matches the authenticated user's session company.
  4. Review authorization logic in code
    Examine the application source code or API handlers for company-specific operations to determine if there is a validation check comparing the requested company ID against the user's authenticated session tenant context.
    Affected if No validation exists to confirm the company ID in the request belongs to the authenticated user's tenant.
  5. Check audit logs for cross-tenant access
    Review application or database audit logs for access patterns where users accessed data belonging to companies different from their own based on login context.
    Affected if Logs show users accessing or modifying records for companies they are not associated with in the user session.

If the application processes POST requests containing a company/tenant ID without validating that the ID matches the authenticated user's assigned company, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization validation to ensure the requested company ID belongs to the authenticated user's session before processing any request. All company-specific operations must verify tenant context matches the authenticated user's tenant.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12686 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data