Security readout for executives and security teams
Plain-English summary
This CVE describes a privacy failure in Tor Browser 9.0.7 on Windows 10 build 10586. A local attacker could recover information about onion services a user visited by analyzing RAM hours after use. The main business concern is exposure of sensitive browsing activity where Tor use is relied on for anonymity.
Executive priority
Prioritize if the organization depends on Tor for sensitive research, investigations, journalism, or whistleblower workflows. For general enterprise environments without Tor Browser 9.0.7 on the specified Windows build, urgency is lower but inventory should confirm exposure.
Technical view
The reported issue is improper memory cleanup in Tor Browser 9.0.7 on Windows 10 build 10586. Residual data in RAM may disclose onion-service visit information to a local attacker. The CVE record does not provide CVSS, CWE, patch details, or broader affected-version data.
Likely exposure
Exposure appears limited to endpoints running Tor Browser 9.0.7 on Windows 10 build 10586, especially shared, monitored, seized, or malware-exposed systems where local memory access is plausible.
Exploitation context
The provided sources describe local information disclosure through RAM analysis. They do not show remote exploitation, public exploitation in the wild, or CISA KEV listing. Exploitation requires local access or equivalent ability to inspect system memory.
Researcher notes
Evidence is sparse. The CVE cites Tor Browser 9.0.7 on Windows 10 build 10586 and one ScienceDirect reference. NVD-style affected product, CVSS, CWE, exploit status, and patch data are absent in the supplied bundle.
Mitigation direction
- Identify any endpoints using Tor Browser 9.0.7 on Windows 10 build 10586.
- Check Tor Browser vendor guidance for supported versions and security updates.
- Avoid using the affected legacy build for anonymity-sensitive activity.
- Restrict local administrative and physical access to systems using privacy tools.
- Review endpoint memory acquisition and forensic handling procedures.
Validation and detection
- Inventory Tor Browser versions and Windows builds on managed endpoints.
- Confirm whether Tor Browser 9.0.7 exists in any standard images.
- Review privacy-sensitive workflows that rely on Tor anonymity.
- Check endpoint controls limiting local memory access.
- Document findings where evidence is unavailable or unmanaged.
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.
CVE-2021-46702 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.sciencedirect.com/science/article/pii/S0167404821001358CVE reference · 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.
