dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2031

CRITICAL · 10.0 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Improper Access Control vulnerability in several internal API endpoints for Google Cloud Application Integration prior to 2026-01-23 allows a remote, unauthenticated attacker to disclose sensitive internal information and execute arbitrary code using specially crafted HTTP requests to inadvertently exposed internal API endpoints.

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 · moderate confidence

Improper access control in Google Cloud Application Integration exposes internal API endpoints to unauthenticated remote attackers. These inadvertently exposed endpoints allow disclosure of sensitive internal information and arbitrary code execution via specially crafted HTTP requests.

MitigationApply the vendor patch (released 2026-01-23) and audit access logs for indicators of compromise; ensure internal API endpoints are not exposed to untrusted networks.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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:Clear

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 Google Cloud Application Integration usage
    Review your Google Cloud project resources to confirm if Application Integration is enabled. Use the Google Cloud Console or gcloud command: gcloud services list --enabled to check for applicationintegration.googleapis.com
    Affected if Application Integration service is enabled in your Google Cloud project
  2. Check Application Integration version
    Navigate to Google Cloud Console > Application Integration > Settings or use APIs explorer to query the service configuration. Compare the deployed version against the 2026-01-23 patch date
    Affected if Running a version released before 2026-01-23
  3. Verify internal API endpoint exposure
    Review your VPC network firewall rules and Cloud IAM policies for Application Integration. Check if internal API endpoints (typically under /api/ or internal paths) are accessible from outside your organization or without authentication. Use VPC flow logs and Cloud Armor policies to inspect traffic sources
    Affected if Internal API endpoints are exposed to the public internet or accessible without authentication
  4. Inspect IAM permissions for Application Integration
    Check the IAM roles assigned to the Application Integration service account and any principals with access to integration endpoints. Review using: gcloud projects get-iam-policy PROJECT_ID --filter="bindings.role:roles/applicationintegration.*"
    Affected if Broad or overly permissive IAM roles allow unauthenticated or public principals to invoke internal APIs
  5. Review API Gateway and load balancer configurations
    Examine Cloud Endpoints, API Gateway, or Cloud Load Balancing configurations that front Application Integration. Check for missing authentication requirements or authentication bypass settings
    Affected if API Gateway or load balancers are configured to allow unauthenticated access to integration endpoints

You are affected if Google Cloud Application Integration is exposed to unauthenticated or public network access AND is running a version older than the 2026-01-23 patch.

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

Apply the vendor patch (released 2026-01-23) and audit access logs for indicators of compromise; ensure internal API endpoints are not exposed to untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2031 — 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-2031 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