dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-11424

HIGH · 8.3 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable 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
A server-side request forgery (SSRF) vulnerability exists in a GraphQL service component shared by Altium Enterprise Server and Altium 365. An authenticated user can submit a request whose input is treated as a URL by the server and used to issue an outbound HTTP GET request without URL validation or destination filtering. The response body is then returned to the user. This allows an authenticated attacker to reach internal services and metadata endpoints that would not otherwise be accessible from the public network, and to retrieve their contents. The impact is information disclosure and internal infrastructure reconnaissance; the request primitive is limited to HTTP GET with no custom headers. Altium Enterprise Server is fixed in 8.1.1; the issue has been remediated in Altium 365 at the service level.

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 Server-Side Request Forgery (SSRF) vulnerability in a GraphQL service component of Altium Enterprise Server and Altium 365. An authenticated user can submit input that the server treats as a URL, causing it to issue outbound HTTP GET requests to arbitrary destinations without validation. This allows attackers to access internal services and metadata endpoints that would be unreachable from the public internet.

MitigationUpdate Altium Enterprise Server to version 8.1.1 or later. For Altium 365, verify with the vendor that the service-level remediation has been applied. Implement network segmentation and egress filtering as defense-in-depth measures.

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:N/VA:N/SC:H/SI:N/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. Confirm Altium product in use
    Identify whether Altium Enterprise Server or Altium 365 is deployed in your environment by reviewing installed software, service listings, or documentation.
    Affected if Altium Enterprise Server is in use and version is unknown or below 8.1.1
  2. Determine Altium Enterprise Server version
    Locate the installed version through the server administration interface, installation directory, or by querying the service about dialog. Compare against the affected range (versions prior to 8.1.1).
    Affected if Version is below 8.1.1
  3. Verify GraphQL endpoint accessibility
    Check if the /graphql or similar GraphQL endpoint is exposed externally or accessible without network segmentation. Attempt a benign request to confirm the endpoint responds.
    Affected if GraphQL endpoint is reachable from untrusted networks or non-admin accounts
  4. Inspect HTTP request logs for internal destinations
    Review server access logs, proxy logs, or outbound request logs for suspicious patterns such as requests to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or internal services.
    Affected if Logs show HTTP requests to internal IPs or metadata endpoints that were not initiated by legitimate internal users
  5. Check for URL validation gaps
    If you have access to test the GraphQL API, attempt a controlled request to an internal endpoint (e.g., http://localhost or 127.0.0.1) using the GraphQL query mechanism to see if the server performs the request without blocking.
    Affected if The server successfully makes outbound requests to internal addresses through the GraphQL API

You are affected if Altium Enterprise Server version is below 8.1.1 and the GraphQL endpoint accepts requests that can reach internal network resources without proper validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Altium Enterprise Server to version 8.1.1 or later. For Altium 365, verify with the vendor that the service-level remediation has been applied. Implement network segmentation and egress filtering as defense-in-depth measures.

Recommended fix High confidence

Altium Enterprise Server 8.1.1 or later

  1. Identify the current version of Altium Enterprise Server or Altium 365 deployment in use
  2. For Altium Enterprise Server: upgrade to version 8.1.1 or later to remediate the SSRF vulnerability
  3. For Altium 365: no customer action required as the issue has been remediated at the service level by Altium
  4. Verify the upgrade was successful by confirming the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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