CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last KEV listing1d
- Last sighting38d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jun 2, 2026
- EUVDENISA, European Unionlisted Jun 2, 2026
- VulnCheck KEVcommercial researchlisted Jun 1, 2026
- CIRCLaggregator, mirrors the abovelisted Jun 2, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.recordedfuture.com/blog/june-2026-cve-landscape
- reported exploitationt.me/xakep_ru/19469
- reported exploitationvulnerability.circl.lu/known-exploited-vulnerabilities-catal
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationsource.android.com/docs/security/bulletin/2026/2026-06-01
5 public reports collected from VulnCheck and CIRCL, first on Jun 1, 2026. Each links to its original source. We have not verified them.
Description
In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.