{"vulnerability": "cve-2026-16424", "sightings": [{"uuid": "ebafcbaf-61e2-4c70-bdad-929a0f6e50d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-16424", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/google-chrome-multiple-vulnerabilities_20260722", "content": "", "creation_timestamp": "2026-07-22T04:45:29.383150Z"}, {"uuid": "6dfb88d4-a834-42ca-9e80-ed64120d61f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-16424", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mraj5tlbai2v", "content": "CVE-2026-16424 - chrome\nGoogle Chrome on Android devices with outdated versions may be at risk of being taken over by a hacker who has already compromised the browser. This could allow the hacker to access\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#chrome #google #CVE #infosec", "creation_timestamp": "2026-07-22T14:16:04.736343Z"}, {"uuid": "4ba3c03e-cb35-4175-916f-98f94e096e4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-16424", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mrale6kak22g", "content": "\ud83d\udd17 CVE : CVE-2026-16413, CVE-2026-16414, CVE-2026-16415, CVE-2026-16416, CVE-2026-16417, CVE-2026-16418, CVE-2026-16419, CVE-2026-16420, CVE-2026-16421, CVE-2026-16422, CVE-2026-16423, CVE-2026-16424", "creation_timestamp": "2026-07-22T14:55:25.353119Z"}]}