Security readout for executives and security teams
Plain-English summary
Lightpanda versions before 0.2.9 could send a user’s session cookies to the wrong place when automation loaded attacker-controlled content. That content could make authenticated requests to another site already logged into in the same Lightpanda session. This creates serious data theft or unauthorized action risk in automation workflows using logged-in browser sessions.
Executive priority
Prioritize remediation for any production or sensitive automation using authenticated Lightpanda sessions. The business risk is unauthorized access or actions through trusted session cookies, with a vendor fix already available.
Technical view
Lightpanda fetch() and XMLHttpRequest ignored credentials mode controls, including fetch credentials settings and XMLHttpRequest.withCredentials. Session cookies were attached to cross-origin HTTP requests regardless of policy. The issue is tracked as CWE-346, affects lightpanda-io/browser before 0.2.9, and is fixed in 0.2.9.
Likely exposure
Exposure is most likely in AI, scraping, test, or automation pipelines that use Lightpanda with authenticated sessions and load untrusted or attacker-controlled origins. Systems not using Lightpanda, or using 0.2.9 or later, are not indicated as affected by the supplied sources.
Exploitation context
The CVSS vector indicates network attackability, low complexity, no privileges, and required user interaction. The supplied data says KEV is false, and no provided source states active exploitation. Exploitation would require attacker-controlled content to run in a Lightpanda session that has relevant victim-origin cookies.
Researcher notes
Focus validation on cookie attachment behavior across fetch() credentials modes and XMLHttpRequest.withCredentials. Do not assume browser-standard credential controls protected older Lightpanda sessions. Evidence is strong for affected versions and fix version, but the supplied sources do not document exploitation in the wild.
Mitigation direction
- Upgrade lightpanda-io/browser to version 0.2.9 or later.
- Review the GitHub advisory and release notes for vendor guidance.
- Avoid mixing authenticated sessions with untrusted origins until upgraded.
- Refresh containers, lockfiles, and automation images that package Lightpanda.
- Invalidate exposed sessions if suspicious cross-origin activity is found.
Validation and detection
- Inventory services, agents, tests, and automation jobs that use Lightpanda.
- Confirm each Lightpanda installation reports version 0.2.9 or later.
- Review dependency locks and container manifests for older Lightpanda builds.
- Identify workflows where authenticated cookies and untrusted origins share one session.
- Check logs for unexpected authenticated cross-origin requests from automation infrastructure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-346: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-52843 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N2.85.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lightpanda-io/browser/security/advisories/GHSA-36mm-v3c2-24ccCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/lightpanda-io/browser/pull/2155CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/lightpanda-io/browser/commit/2cdaac780bed65db98bbb6ed2ad5bc6011863c76CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/lightpanda-io/browser/releases/tag/0.2.9CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Origin Validation Error
Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.