OAuth token disclosure via permissive backup permissions
Published Sep 22, 2026 · Updated Sep 22, 2026
Information disclosure in sooperset MCP Atlassian before 0.22.0 allows local users to read plaintext OAuth access and refresh tokens. OAuthConfig._save_tokens_to_file writes the fallback token file using permissions inherited from the process umask instead of forcing an owner-only mode. Exposure requires fallback-file storage and a group- or world-readable umask, and a stolen refresh token preserves Atlassian access.
Summary
What happened
Information disclosure in sooperset MCP Atlassian before 0.22.0 allows local users to read plaintext OAuth access and refresh tokens. OAuthConfig._save_tokens_to_file writes the fallback token file using permissions inherited from the process umask instead of forcing an owner-only mode. Exposure requires fallback-file storage and a group- or world-readable umask, and a stolen refresh token preserves Atlassian access.
The record
- CVE
- CVE-2026-77256
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- sooperset
- Product
- MCP Atlassian
- Classifications
- T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.22.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started