Habr•November 22, 2026•🇷🇺Translated from Russian

Chrome Researcher Edits Own VRP Reward to $1.3M in Bug Tracker Prank, Triggering AI Misinformation Spread

Security researcher Lyra Rebane has revealed how a simple joke in Google’s internal bug tracker turned her into an apparent Chrome millionaire in the eyes of multiple AI systems.

Rebane, who has 14 CVEs to her name in Chromium, reported a logical vulnerability in the Background Fetch API in 2022. The flaw allowed an attacker to build browser botnets simply by luring victims to a website or embedding an iframe. The issue remained open for years until Google finally patched it in February 2026 and paid the standard $1,000 reward.

Months later, Rebane was unexpectedly granted verifier rights in the Buganizer tracker. With edit access, she changed the vrp-reward field to $1,333,337 — the highest sum ever recorded in the Google Vulnerability Reward Program. She then posted a two-part thread on X (formerly Twitter) announcing the record payout and showing the edit in a short video.

The thread quickly gained hundreds of likes. X’s Community Notes feature added context, but an experimental AI-generated note wrongly accused her of editing the screenshot. After Rebane complained, the note was removed. AI-driven news accounts such as “Daily Vibe Casting” then began summarizing the thread as fact, and Google’s own search results started presenting her as a millionaire when users searched for the largest Chrome bug bounties.

Similar AI-generated answers appeared in Kagi, DuckDuckGo, and Bing, all citing the original tweet or her later write-up. Google VRP later contacted Rebane to discourage further edits to reward fields.

The episode demonstrates how easily a single viral post can poison AI training data and search results, even when the original author later clarifies the joke.

Related articles

Securitylab•Vulnerabilities & Exploits

Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK

Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.

Habr•Vulnerabilities & Exploits

F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway

Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.

Securitylab•Vulnerabilities & Exploits

NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2

On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.

安全客•Vulnerabilities & Exploits

Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4

China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.