Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify or inject XSS payload on forum.openai.com
-
DeliveryDeliver link to victim with Atlas installed
-
ExploitVictim passively loads malicious forum page
-
ExecutionInjected script invokes Atlas privileged browser APIs
-
ImpactExfiltrate victim browser history or manipulate open tabs
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Three specific conditions must all be satisfied: (1) the victim must have OpenAI Atlas version prior to 1.2025.288.15 installed and active in their browser; (2) the attacker must have a viable XSS injection point on forum.openai.com - a separate, prerequisite vulnerability on that platform - through which a malicious script can be served; (3) the victim must passively browse to the XSS-affected forum.openai.com page (UI:P - passive user interaction, such as visiting a link or loading a page, is required). Limiting factors: exploitation is not automatable (AU:N per CVSS 4.0 supplemental), attack complexity is rated high (AC:H) due to the chained XSS dependency, and impact is scoped to the victim component only (SC:N, SI:N, SA:N) - the attacker cannot pivot to other systems. There is no authentication requirement for the attacker (PR:N), but the target must be a specific Atlas user visiting the specific vulnerable forum content. |
| Impact | The CVSS 4.0 score of 6.0 reflects a moderate-severity finding. Key attenuating signals: AC:H indicates high attack complexity due to the prerequisite XSS chain; UI:P requires passive victim interaction (browsing the malicious forum page); and AU:N confirms the attack is not automatable. Impact is limited to VC:H (confidentiality of the vulnerable component - browser history exposure) with no integrity or availability impact (VI:N, VA:N, SC:N, SI:N, SA:N). The CVSS 4.0 supplemental metrics reinforce low urgency: U:Green, RE:L (low recovery effort), and V:D (diffuse value density, meaning broad but low-value targeting). EPSS at 0.02% (4th percentile) is consistent with the high complexity bar. There is no CISA KEV listing. A public blog post at hacktron.ai describes the attack technique, which elevates awareness risk but is not confirmed as weaponized exploit code. Overall: real vulnerability with meaningful confidentiality impact, but practical exploitation requires chaining two conditions (Atlas installed AND forum XSS reachable), making mass exploitation unlikely and targeted attacks the realistic threat model. |
| Exploit ScenarioDerived | An attacker identifies or plants an XSS payload on forum.openai.com, then lures a target user with OpenAI Atlas (< 1.2025.288.15) installed to view the malicious forum content. When the victim passively browses the compromised forum page, the injected script executes within the *.openai.com trust context recognized by Atlas and invokes the privileged browser APIs, silently exfiltrating the victim's browser history or manipulating their open tabs. The hacktron.ai security blog documents this attack surface, suggesting the technique is publicly known, though a ready-to-use exploit has not been confirmed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 05, 2026
OpenAI Atlas before 1.2025.288.15 improperly exposed privileged browser APIs - including browser history access and tab open/close controls - to any web content loaded from *.openai.com origins, including the publicly accessible forum.openai.com. Because forum.openai.com harbored an independent cross-site scripting vulnerability, an attacker could chain the two weaknesses: inject a script via the forum XSS, which then silently invokes Atlas's privileged APIs against a visiting victim. No public exploit or CISA KEV listing has been confirmed at time of analysis, though a public security research blog (hacktron.ai) describes the attack surface; the EPSS score of 0.02% (4th percentile) reflects low observed exploitation probability.
RemediationAI
The primary fix is upgrading to OpenAI Atlas 1.2025.288.15 or later, which restricts privileged API access to *.chatgpt.com origins only, eliminating forum.openai.com from the trusted origin set. This is a vendor-released patch confirmed in the CVE description and EUVD-2026-34776; users should apply it immediately. If upgrade is not immediately possible, a compensating control is to disable or uninstall the OpenAI Atlas extension/application until the patch can be applied - this fully eliminates the attack surface at the cost of losing Atlas functionality. Alternatively, organizations with network filtering capabilities could block access to forum.openai.com at the proxy or DNS layer for Atlas-installed endpoints, which would prevent the XSS delivery vector; however, this does not fix the root improper access control and would only address the forum.openai.com XSS pathway, not potential future XSS vulnerabilities on other *.openai.com subdomains. Reference advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-11326.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenAI Atlas is a browser extension or companion application (CPE: cpe:2.3:a:openai:openai_atlas:*:*:*:*:*:*:*:*) that exposes privileged browser APIs - capabilities not available to ordinary web pages - intended for controlled use. The root cause is CWE-284 (Improper Access Control): Atlas granted these sensitive API bindings to the overly broad *.openai.com origin trust boundary, which includes forum.openai.com, a user-generated content platform with its own XSS exposure. The CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:N/UI:P) reflects a network-reachable, chained attack requiring high complexity because successful exploitation depends on an independently exploitable XSS condition on forum.openai.com co-occurring with a victim who has Atlas installed and browses the affected forum. The fix implemented in 1.2025.288.15 narrows the privileged API trust scope to *.chatgpt.com, eliminating the overly permissive origin grant.
Know when Openai Atlas gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/AU:N/V:D/RE:L/U:Green
Primary rating from Vendor (OAI) · only source for this CVE.
CVSS VectorVendor: OAI
Lifecycle Timeline
3DescriptionCVE.org
OpenAI Atlas before 1.2025.288.15 exposed privileged browser APIs to web content on *.openai.com origins. A cross-site scripting vulnerability in forum.openai.com could be used to access these functions, allowing access to browser history information and the ability to open or close tabs. OpenAI Atlas 1.2025.288.15 narrows access to these APIs to *.chatgpt.com; users should upgrade to 1.2025.288.15 or later.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-34776
GHSA-x355-jg5j-p4h6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB