CVE-2025-58445: Github.com/runatlantis/atlantis Atlantis Exposes Service Version Publicly Vulnerability

LOW
Advisory Identifier: GHSA-xh7v-965r-23f7
CVSS 7.5
CWE-200
Published
Advisory Summary

CVE-2025-58445 is a LOW (CVSS 7.5) atlantis exposes service version publicly vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/runatlantis/atlantis libraries in the Go ecosystem. The issue involves atlantis exposes service version publicly on /status api endpoint. Remediation is available in the latest vendor maintenance releases.

CVE-2025-58445 at a Glance

CVE Identifier CVE-2025-58445
GHSA Identifier GHSA-xh7v-965r-23f7
Severity LOW
CVSS v3.1 Base Score 7.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/runatlantis/atlantis
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-58445

To remediate this vulnerability, upgrade all affected Github.com/runatlantis/atlantis dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/runatlantis/atlantis fixed: Latest secure release
Upgrade github.com/runatlantis/atlantis to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/runatlantis/atlantis

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-58445, inspect your project dependencies for Github.com/runatlantis/atlantis:

inspect dependencies for github.com/runatlantis/atlantis

Analyze the terminal output to locate any version of Github.com/runatlantis/atlantis in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Github.com/runatlantis/atlantis, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Atlantis publicly exposes detailed version information on its `/status` endpoint. This information disclosure could allow attackers to identify and target known vulnerabilities associated with the specific versions, potentially compromising the service's security posture. ### Details The `/status` endpoint in Atlantis returns not only a health check but also detailed version and build information. This disclosure violates the principle of minimizing exposed sensitive metadata and can be leveraged by adversaries to correlate the version information with public vulnerability databases, including CVE listings. Although Atlantis is a public repository maintained by an external team, reducing this exposure can lessen the overall risk of targeted attacks. For example, the source code handling the `/status` endpoint exposes version details that allow one to infer software dependencies and system configurations. Best practices, including guidelines from the [OWASP Top 10](https://owasp.org/www-project-top-ten/) and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information. ### PoC 1. Issue a GET request to `http://<atlantis-host>/status` using a tool like `curl` or a web browser. 2. Note that the API response includes detailed version and build information. 3. Verify that no authentication is required to access the endpoint, leading to public exposure. 4. Cross-reference the disclosed version with public vulnerability databases (e.g., [NVD](https://nvd.nist.gov)) for likely vulnerabilities. ### Impact The vulnerability falls under the category of information disclosure. Attackers could use the version details to scan public vulnerability repositories and tailor attacks based on known flaws in that particular version. This could potentially escalate into a broader compromise if the underlying software has exploitable vulnerabilities. Therefore, the affected parties include any users or administrators who rely on Atlantis, as well as the maintainers who are responsible for keeping the service secure. ### CVS Severity Assessment Based on the current circumstances, this issue is assessed as **CVS Severity: LOW**. However, if the disclosed version is known to contain critical vulnerabilities, the severity rating could be re-evaluated to **Medium**. It is recommended to restrict this information to safeguarded internal channels to mitigate the risk of targeted attacks.

CVE-2025-58445 Affected Github.com/runatlantis/atlantis Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
github.com/runatlantis/atlantis
Go
≤ 0.35.1

References

Frequently Asked Questions

What is CVE-2025-58445?
CVE-2025-58445 is a security vulnerability in Github.com/runatlantis/atlantis involving Atlantis Exposes Service Version Publicly on /status API Endpoint under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/runatlantis/atlantis versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/runatlantis/atlantis.
What version fixes CVE-2025-58445?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/runatlantis/atlantis affected?
Yes, github.com/runatlantis/atlantis is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2025-58445?
CVE-2025-58445 has a CVSS v3.1 base score of 7.5 (LOW) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-58445?
CVE-2025-58445 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for CVE-2025-58445?
Run the dependency tree command: 'inspect dependencies for github.com/runatlantis/atlantis'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xh7v-965r-23f7",
  "modified" : "2025-09-13T03:03:00Z",
  "published" : "2025-09-05T21:18:47Z",
  "aliases" : [ "CVE-2025-58445" ],
  "summary" : "Atlantis Exposes Service Version Publicly on /status API Endpoint",
  "details" : "### Summary\nAtlantis publicly exposes detailed version information on its `/status` endpoint. This information disclosure could allow attackers to identify and target known vulnerabilities associated with the specific versions, potentially compromising the service's security posture.\n\n### Details\nThe `/status` endpoint in Atlantis returns not only a health check but also detailed version and build information. This disclosure violates the principle of minimizing exposed sensitive metadata and can be leveraged by adversaries to correlate the version information with public vulnerability databases, including CVE listings. Although Atlantis is a public repository maintained by an external team, reducing this exposure can lessen the overall risk of targeted attacks.\n\nFor example, the source code handling the `/status` endpoint exposes version details that allow one to infer software dependencies and system configurations. Best practices, including guidelines from the [OWASP Top 10](https://owasp.org/www-project-top-ten/) and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information.\n\n### PoC\n1. Issue a GET request to `http://<atlantis-host>/status` using a tool like `curl` or a web browser.\n2. Note that the API response includes detailed version and build information.\n3. Verify that no authentication is required to access the endpoint, leading to public exposure.\n4. Cross-reference the disclosed version with public vulnerability databases (e.g., [NVD](https://nvd.nist.gov)) for likely vulnerabilities.\n\n### Impact\nThe vulnerability falls under the category of information disclosure. Attackers could use the version details to scan public vulnerability repositories and tailor attacks based on known flaws in that particular version. This could potentially escalate into a broader compromise if the underlying software has exploitable vulnerabilities. Therefore, the affected parties include any users or administrators who rely on Atlantis, as well as the maintainers who are responsible for keeping the service secure.\n\n### CVS Severity Assessment\nBased on the current circumstances, this issue is assessed as **CVS Severity: LOW**. However, if the disclosed version is known to contain critical vulnerabilities, the severity rating could be re-evaluated to **Medium**. It is recommended to restrict this information to safeguarded internal channels to mitigate the risk of targeted attacks.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/runatlantis/atlantis"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.35.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/runatlantis/atlantis/security/advisories/GHSA-xh7v-965r-23f7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-58445"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/runatlantis/atlantis"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-05T21:18:47Z",
    "nvd_published_at" : "2025-09-06T20:15:30Z"
  }
}