Summary
Atlantis Exposes Service Version Publicly on /status API Endpoint
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 and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information.
PoC
- Issue a GET request to
http://<atlantis-host>/statususing a tool likecurlor a web browser. - Note that the API response includes detailed version and build information.
- Verify that no authentication is required to access the endpoint, leading to public exposure.
- Cross-reference the disclosed version with public vulnerability databases (e.g., NVD) for likely vulnerabilities.
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.
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.
CVE-2025-58445 has a CVSS score of 7.5 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-58445? CVE-2025-58445 is a low-severity security vulnerability in github.com/runatlantis/atlantis (go), affecting versions <= 0.35.1. No fixed version is listed yet.
- How severe is CVE-2025-58445? CVE-2025-58445 has a CVSS score of 7.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/runatlantis/atlantis are affected by CVE-2025-58445? github.com/runatlantis/atlantis (go) versions <= 0.35.1 is affected.
- Is there a fix for CVE-2025-58445? No fixed version is listed for CVE-2025-58445 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2025-58445 exploitable, and should I be worried? Whether CVE-2025-58445 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-58445 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.