{"vulnerability": "cve-2025-48615", "sightings": [{"uuid": "8f58eb21-3476-464b-a2b9-96c1e425a29f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-48615", "type": "seen", "source": "https://notnow.dev/objects/825821a4-404d-4687-b0b4-c981516d58a5", "content": "According to GrapheneOS, the SQLite issue marked as exploited in the wild in the June Android Security Bulletin was originally patched in SQLite 3.44.5 from July 2025:https://grapheneos.social/@GrapheneOS/116681501156712831https://github.com/sqlite/sqlite/commit/710858bca3e6f0cc1d5d74101a1b444b3c7214ffHowever, searching for this commit shows that patch is for CVE-2025-6965.I guess CVE-2025-48615 is a duplicate/variant?You may remember CVE-2025-6965 as the bug that Project Zero's \"Big Sleep\" AI discovered, after Project Zero received reports of a bug \"known only to threat actors and was at risk of being exploited\", (https://blog.google/innovation-and-ai/technology/safety-security/cybersecurity-updates-summer-2025/)I guess that explains why it's marked as exploited in the wild in the bulletin.", "creation_timestamp": "2026-06-04T04:54:51.892785Z"}, {"uuid": "6cd01ca0-c433-4f48-b57a-781910c14ef4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-48615", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/samsung-products-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T20:00:00.000000Z"}, {"uuid": "d79b4b90-dd6e-4f7a-aec9-34d1d43f560d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-48615", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/android-multiple-vulnerabilities_20260602", "content": "", "creation_timestamp": "2026-06-01T18:00:00.000000Z"}]}