Skip to main content
VulnerabilityPublished Updated

CVE-2025-58445: runatlantis atlantis · Information Exposure

Affects runatlantis atlantisSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
runatlantis atlantisAffected
  • <=0.35.1
Fixed in–

AI-suggested

Given the absence of an official fix, European organizations should implement specific mitigations to reduce exposure. First, restrict access to the Atlantis /status endpoint by network segmentation and firewall rules, allowing only trusted internal IPs or VPN users to access the service. Second, implement authentication and authorization layers in front of Atlantis endpoints using reverse proxies or API gateways to prevent unauthorized access. Third, monitor and log all access to Atlantis endpoints to detect unusual or unauthorized queries, enabling rapid incident response. Fourth, consider upgrading Atlantis to versions beyond 0.35.1 once a patch is released or evaluate alternative tools with better security postures. Fifth, conduct regular security assessments of the DevOps pipeline to identify and remediate information disclosure risks. Finally, educate DevOps teams about the risks of exposing version information and enforce secure configuration management practices to minimize unnecessary information leakage.

Description

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. All versions of Atlantis publicly expose detailed version information through 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. This issue does not currently have a fix.

References

Community reviews

Loading reviews…