Event JSON
{
"id": "e4bb1862182d6e1a74d75ac8250fb1863b0ad0e656fa38b7e1a15c9d93d6de3a",
"pubkey": "6b0666343642010ae414debcfb5d1999902001dbf80fd8dad81f0f46c11eca87",
"created_at": 1790997436,
"kind": 1,
"tags": [
[
"t",
"google"
],
[
"t",
"chrome"
],
[
"proxy",
"https://infosec.exchange/@ssvc/117374808023587810",
"web"
],
[
"t",
"cve"
],
[
"proxy",
"https://infosec.exchange/ap/users/117202824925377048/statuses/117374808023587810",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/ap/users/117202824925377048/statuses/117374808023587810",
"pink.momostr"
],
[
"-"
]
],
"content": "Google Chrome published an empty blog post as a security advisory on Thursday afternoon. They filled it out in the past day, but don't make it easy to grasp the severity of their bugs.\n\nFor example, \"Critical CVE-2026-103628: Out of bounds write in WebGL.\" is actually a CVSSv3.1: **9.6 critical** because it allows a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. You'd have to chase down those details yourself on cve.org or elsewhere. \n\nhttps://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html\n\n#google #chrome #CVE",
"sig": "f434e3ef32e3123e11ccc7584f10777470f84604ea61ba2b044b442ef1b72c51c0d6479d9ad10a3b9437f5383b158b7c1826e4e83fd479313753b7554cdac3fa"
}