Password disclosure via sandboxed-content autofill
Published Feb 20, 2023 · Updated Mar 18, 2025
Information disclosure in GNOME Web 43.0 and earlier allows remote attackers to steal saved passwords through sandboxed web content. Its password manager autofills login fields without rejecting sandboxed documents whose origin is null, exposing credentials to the page. A victim must have saved credentials for the matching site and load the crafted content; the demonstrated result is password disclosure.
Summary
What happened
Information disclosure in GNOME Web 43.0 and earlier allows remote attackers to steal saved passwords through sandboxed web content. Its password manager autofills login fields without rejecting sandboxed documents whose origin is null, exposing credentials to the page. A victim must have saved credentials for the matching site and load the crafted content; the demonstrated result is password disclosure.
The record
- CVE
- CVE-2023-26081
- Published
- Feb 20, 2023
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1555.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- Sandboxed autofill proof of conceptproof of concept · unverified
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo