Memory corruption via use-after-free
Published May 30, 2025 · Updated May 30, 2025
Use-after-free in Yandex Browser for Desktop before 24.4.0.682 allows attackers to corrupt browser memory via unspecified vectors. Yandex has not published the affected component, the operation that frees an object, or the untrusted input that later accesses it. Exploitation requires passive user interaction and additional conditions, while the published record does not establish whether memory corruption yields code execution.
Summary
What happened
Use-after-free in Yandex Browser for Desktop before 24.4.0.682 allows attackers to corrupt browser memory via unspecified vectors. Yandex has not published the affected component, the operation that frees an object, or the untrusted input that later accesses it. Exploitation requires passive user interaction and additional conditions, while the published record does not establish whether memory corruption yields code execution.
The record
- CVE
- CVE-2023-26226
- Published
- May 30, 2025
- Updated
- May 30, 2025
- Vendor
- Yandex
- Product
- Yandex Browser
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 30, 2025CVE publishedPublication date reported by the CVE source.
- May 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <24.4.0.682
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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