dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-25076

HIGH · 7.3 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
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
Anchore Enterprise versions before 5.25.1 contain an SQL injection vulnerability in the GraphQL Reports API. An authenticated attacker that is able to access the GraphQL API could execute arbitrary SQL instructions resulting in modifications to the data contained in the Anchore Enterprise database.

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

Anchore Enterprise versions before 5.25.1 contain a SQL injection vulnerability in the GraphQL Reports API. An authenticated attacker with access to the GraphQL API can inject arbitrary SQL instructions through the vulnerable endpoint, allowing modification of data stored in the Anchore Enterprise database.

MitigationUpgrade Anchore Enterprise to version 5.25.1 or later to remediate this vulnerability. Since this is an authenticated SQL injection, restricting API access alone is insufficient—the patch must be applied.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 Anchore Enterprise is installed
    Identify whether Anchore Enterprise is running in your environment. This may be via container inspection, service listing, or checking for anchore-related processes.
    Affected if Anchore Enterprise is not present in the environment, the CVE does not apply.
  2. Determine the installed version of Anchore Enterprise
    Retrieve the running Anchore Enterprise version. This is typically accessible via the Anchore CLI command 'anchore-cli --version', the API endpoint '/health', or the container/ deployment metadata.
    Affected if Unable to determine the version, manual review of deployment artifacts is required.
  3. Compare the installed version to 5.25.1
    Check if the installed version is earlier than 5.25.1. Versions before 5.25.1 are affected; version 5.25.1 and later are not.
    Affected if The installed version is before 5.25.1, indicating the environment may be vulnerable.
  4. Verify GraphQL API is exposed
    Check whether the GraphQL API endpoint is accessible in your deployment. This is typically at the '/graphql' path. Inspect your reverse proxy, API gateway, or network access controls to confirm the endpoint is reachable.
    Affected if The GraphQL API is not exposed or accessible, the attack surface for this specific vulnerability is reduced.
  5. Confirm authentication is configured for the API
    Review whether the Anchore Enterprise GraphQL API requires authentication. Since this is an authenticated SQL injection, an attacker needs valid credentials. Check if API authentication is enabled and accessible to users.
    Affected if The API is publicly accessible without authentication, the risk is higher; however, the patch is still required regardless of authentication status.

If Anchore Enterprise is installed with a version before 5.25.1 and the GraphQL Reports API is accessible, the environment is likely affected and requires the 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.

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

Upgrade Anchore Enterprise to version 5.25.1 or later to remediate this vulnerability. Since this is an authenticated SQL injection, restricting API access alone is insufficient—the patch must be applied.

Recommended fix High confidence

5.25.1

  1. 1. Identify current Anchore Enterprise version by checking the running containers or deployment manifests
  2. 2. Create a complete backup of the Anchore Enterprise database to ensure data can be restored if needed
  3. 3. Review Anchore Enterprise 5.25.1 release notes for any known migration requirements or prerequisites
  4. 4. Test the upgrade in a non-production/staging environment first to verify compatibility
  5. 5. Deploy Anchore Enterprise version 5.25.1 or later in production following standard upgrade procedures
  6. 6. Verify the GraphQL Reports API is functioning correctly after upgrade
  7. 7. Validate that the SQL injection vulnerability is no longer present through security testing
Caveat Review release notes for any configuration or API changes between current version and 5.25.1; test thoroughly in staging before production deployment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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