CVE-2026-39039: n/a
In BharatMLStack up to and including v1.3.0, Trufflebox UI stores the JWT authentication token, full user object, and session ID in the browser's localStorage, which is fully accessible to any JavaScript running on the page.
AI Analysis
Technical Summary
CVE-2026-39039 identifies that in BharatMLStack versions up to and including 1.3.0, the Trufflebox UI stores JWT authentication tokens, complete user objects, and session IDs in the browser's localStorage. Since localStorage is accessible by all JavaScript executing on the page, this practice can lead to exposure of sensitive authentication information if malicious scripts are present or injected.
Potential Impact
The exposure of JWT tokens, user objects, and session IDs in localStorage can allow attackers who manage to execute JavaScript on the affected page to steal authentication credentials. This could lead to unauthorized access or session hijacking. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running untrusted JavaScript on pages using the affected versions and consider alternative secure storage mechanisms for sensitive tokens instead of localStorage.
CVE-2026-39039: n/a
Description
In BharatMLStack up to and including v1.3.0, Trufflebox UI stores the JWT authentication token, full user object, and session ID in the browser's localStorage, which is fully accessible to any JavaScript running on the page.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-39039 identifies that in BharatMLStack versions up to and including 1.3.0, the Trufflebox UI stores JWT authentication tokens, complete user objects, and session IDs in the browser's localStorage. Since localStorage is accessible by all JavaScript executing on the page, this practice can lead to exposure of sensitive authentication information if malicious scripts are present or injected.
Potential Impact
The exposure of JWT tokens, user objects, and session IDs in localStorage can allow attackers who manage to execute JavaScript on the affected page to steal authentication credentials. This could lead to unauthorized access or session hijacking. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running untrusted JavaScript on pages using the affected versions and consider alternative secure storage mechanisms for sensitive tokens instead of localStorage.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-06T00:00:00.000Z
- State
- PUBLISHED
Threat ID: 6aa984ed55bf5e2cf52bbba3
Added to database: 09/15/2026, 17:48:29 UTC
Last enriched: 09/15/2026, 18:02:26 UTC
Last updated: 09/16/2026, 02:11:04 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.