How severe is CVE-2025-58445?

No CVSS score has been assigned to CVE-2025-58445 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-58445?

CVE-2025-58445 affects the following packages: github.com/runatlantis/atlantis (Go). Ecosystems affected: Go.

How do I fix CVE-2025-58445?

The records we use list no patched version of github.com/runatlantis/atlantis for CVE-2025-58445. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2025-58445 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/runatlantis/atlantis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-58445 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2025-58445 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-58445 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-58445?

CVE-2025-58445 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-58445?

CVE-2025-58445 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-58445 published, and has it been updated?

CVE-2025-58445 was published on September 6, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-58445 — atlantis

CVE-2025-58445 is a Information Exposure vulnerability in github.com/runatlantis/atlantis. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Atlantis Exposes Service Version Publicly on /status API Endpoint

Also known asGHSA-xh7v-965r-23f7GO-2025-3940

Published

Sep 6, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-58445.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/runatlantis/atlantis

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information.

PoC

Issue a GET request to http://<atlantis-host>/status using a tool like curl or 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.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/runatlantis/atlantis`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

atlantisrunatlantis

≤ 0.35.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/runatlantis/atlantis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/runatlantis/atlantis for CVE-2025-58445. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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 databas

O3 Security · Impact-Aware SCA

Is CVE-2025-58445 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works