dbcve.org
AtlasApplication · Apache

CVE-2026-40563

HIGH · 8.1 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
87/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
Description: Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Atlas Apache Atlas exposes a DSL search endpoint that accepts user-supplied query strings. Attacker can alter Gremlin traversal logic within grammar-allowed characters to access unintended data Affect Version: This issue affects Apache Atlas: from 0.8 through 2.4.0. For the affect version >= 2.0, vulnerability is only when Atlas is deployed with below non-default configuration. atlas.dsl.executor.traversal=false Mitigation: Users are recommended to upgrade to version 2.5.0, which fixes the issue.

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

Apache Atlas contains a Code Injection vulnerability in its DSL search endpoint. Attackers can manipulate user-supplied query strings to alter Gremlin traversal logic and access unintended data. Versions 0.8 through 2.4.0 are affected; for versions >=2.0, exploitation requires the non-default configuration atlas.dsl.executor.traversal=false.

MitigationUpgrade to Apache Atlas version 2.5.0. For deployments with the vulnerable non-default configuration setting, ensure the configuration is reviewed during the upgrade process.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AtlasApplication
Affected:>= 0.8, < 2.5.0

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

CVSS:3.1/AV:N/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. Identify Apache Atlas version
    Check the Atlas web interface version page, startup logs, or JAR file names in the Atlas installation directory for a version number matching >= 0.8 and < 2.5.0
    Affected if The installed version falls within 0.8 through 2.4.x inclusive
  2. Confirm DSL search endpoint is accessible
    Attempt to access the Atlas DSL search REST endpoint (typically /api/atlas/v2/search/dsl) or verify in the Atlas configuration that the DSL search functionality is enabled
    Affected if The DSL endpoint responds to requests and accepts query input
  3. Check traversal executor configuration
    Locate the atlas-application.properties file (commonly in conf/ under the Atlas home directory) and inspect the setting atlas.dsl.executor.traversal
    Affected if The setting is absent, set to true, or not explicitly set to false (default behavior enables traversal)
  4. Verify DSL endpoint is not secured
    Review Atlas web server configuration or network access controls to determine if the DSL endpoint is exposed without additional authentication or authorization controls
    Affected if The endpoint is accessible without additional security measures beyond basic authentication

You are affected if Apache Atlas version is 0.8 through 2.4.x and the DSL search endpoint with Gremlin traversal is enabled and accessible in your environment.

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
Upgrade available Upgrade to 2.5.0 or later
Fixed in 2.5.0
Interim mitigation

Upgrade to Apache Atlas version 2.5.0. For deployments with the vulnerable non-default configuration setting, ensure the configuration is reviewed during the upgrade process.

Recommended fix High confidence

2.5.0

  1. 1. Backup your current Apache Atlas installation, configuration files, and data directories
  2. 2. Review Apache Atlas 2.5.0 release notes and upgrade documentation for any migration requirements
  3. 3. Download Apache Atlas version 2.5.0 from the official Apache distribution repository (archive.apache.org)
  4. 4. Stop the running Apache Atlas service
  5. 5. Install Apache Atlas 2.5.0 using your deployment method (binary distribution or other)
  6. 6. Migrate your existing configuration files to the new version, ensuring any custom settings are preserved
  7. 7. Start the Apache Atlas 2.5.0 service
  8. 8. Verify the upgrade by testing the DSL search endpoint and confirming the vulnerability is resolved
Caveat Review 2.5.0 release notes for any breaking changes between your current version and 2.5.0; major version upgrades may require configuration or data migration

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

Fix this in Atlas Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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