dbcve.org
AtlasApplication · Apache

CVE-2025-62198

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 can perform XSS. This issue affects Apache Atlas versions 2.4.0 and earlier. 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

An authenticated user can perform cross-site scripting (XSS) attacks in Apache Atlas versions 2.4.0 and earlier. The vulnerability allows authenticated users to inject malicious scripts through the application, likely via user-supplied input fields that are not properly sanitized before rendering.

MitigationUpgrade Apache Atlas to version 2.5.0 or later. As a temporary measure, implement input validation and output encoding on all user-facing fields, and restrict user permissions where possible.

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:< 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Determine installed Apache Atlas version
    Run 'atlas_version.py' script in the Atlas bin directory, check pom.xml version, or query the Atlas REST API endpoint /api/atlas/version
    Affected if The version shown is 2.4.0 or any version earlier than 2.5.0
  2. Verify Atlas web interface is accessible
    Confirm the Atlas web UI is reachable on the configured port (typically 21000) by accessing the login page
    Affected if The web interface is accessible and responds to HTTP requests
  3. Confirm user authentication is enabled
    Check that Atlas is configured to require authentication for API and web UI access, rather than running in anonymous mode
    Affected if Authentication is enabled and user accounts can be created or managed in the system
  4. Identify user-facing input fields
    Review application logs or network traffic for any user-supplied data that gets rendered back in the web interface without encoding
    Affected if The application displays user input in the UI (search fields, tag names, description fields, etc.)
  5. Check for recent XSS indicators
    Examine Atlas server logs for suspicious script tags, unusual HTML fragments, or javascript: URI schemes in user-created entities, classifications, or comments
    Affected if Logs contain any HTML/script injection patterns in user input fields

A user is affected if Apache Atlas version is 2.4.0 or earlier and the web interface with user authentication is enabled, allowing user-supplied input to be rendered in the UI.

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 Apache Atlas to version 2.5.0 or later. As a temporary measure, implement input validation and output encoding on all user-facing fields, and restrict user permissions where possible.

Recommended fix High confidence

Apache Atlas 2.5.0

  1. 1. Back up your existing Apache Atlas data, database, and configuration files before proceeding with the upgrade.
  2. 2. Download Apache Atlas version 2.5.0 from the official Apache download mirrors or the Apache Atlas release page.
  3. 3. Stop the currently running Apache Atlas instance.
  4. 4. Install or extract Apache Atlas 2.5.0 to your target directory, preserving your configuration files or merging them with the new configuration templates as needed.
  5. 5. Start the Apache Atlas 2.5.0 service.
  6. 6. Verify that the application is running correctly and test that the XSS vulnerability is no longer present.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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