Quick answers
- Is CVE-2026-77256 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77256 being exploited in the wild.
- How severe is CVE-2026-77256?
- Informational severity, published 22 September 2026.
- Which products and versions are affected?
- Sooperset Mcp-Atlassian prior to 0.22.0.
- Is there a fix for CVE-2026-77256?
- A patch was published on 2026-07-10: Fix merged in version 0.22.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77256 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-77256?
- Check whether you run Sooperset Mcp-Atlassian at an affected version. 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 exists in OAuthConfig._save_tokens_to_file, which writes plaintext OAuth refresh and access tokens to a file with default permissions based on the process umask. Under permissive umask configurations, other local users can read this backup file and extract the refresh token to maintain Atlassian access. The fix in version 0.22.0 restricts file permissions to prevent unauthorized local access.
Affected products
- sooperset MCP Atlassian prior to 0.22.0
Timeline
- 2026-09-22: disclosed
- 2026-07-10: patched: Fix merged in version 0.22.0