Quick answers
- Is CVE-2026-82282 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82282 being exploited in the wild.
- How severe is CVE-2026-82282?
- High severity, with a CVSS score of 8, published 28 August 2026.
- Which products and versions are affected?
- Runatlantis Atlantis through 0.47.1.
- Is there a fix for CVE-2026-82282?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82282 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82282?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the /github-app/setup endpoint of Atlantis through version 0.47.1. The endpoint fails to enforce authentication checks before exposing GitHub App configuration details, including the RSA private key and webhook secret used for GitHub integration. An unauthenticated attacker with network access to the Atlantis server can intercept or observe the GitHub redirect during setup to extract these credentials. Once obtained, the attacker can mint installation tokens and forge webhook payloads, enabling unauthorized access to repositories and CI/CD pipeline manipulation. The vulnerability requires network access to the endpoint but no prior authentication or user interaction.
Affected products
- Runatlantis Atlantis through 0.47.1
Timeline
- 2026-08-28: disclosed