GreyNoise and Blackpoint tracked an AI-assisted actor using OpenAI Codex and DeepSeek agents to exploit PaperCut flaws across 440+ instances in 48 countries.
A suspected Russian-speaking actor exploited the CVE-2026-81578 authentication bypass and CVE-2026-82078 RCE chain in PaperCut NG/MF, compromising at least 440 instances across 395 organizations in 48 countries, heavily targeting education in the US, UK, France, and elsewhere. The actor used hundreds of AI agents powered by OpenAI Codex and DeepSeek plus tools like Mimikatz, SharpHound, Certipy, Rubeus, and Impacket, reaching domain admin at 12 victims and full domain admin at a US high school within seven minutes. Post-exploitation included registry hive collection and Metasploit/Meterpreter payloads, with origin traced to IP 45.142.193.132.
ZDI published a Pwn2Own advisory for CVE-2026-19590, enabling remote code execution in OpenAI's Codex agent via system or configuration control.
Zero Day Initiative advisory ZDI-26-648 documents an External Control of System or Configuration Setting vulnerability in OpenAI Codex, demonstrated at Pwn2Own. A remote attacker could achieve arbitrary code execution, with user interaction required such as opening malicious content. The flaw is tracked as CVE-2026-19590 with a CVSS rating of 7.8. No exploitation in the wild is reported.
Google patches actively exploited Chrome V8 zero-day CVE-2026-87491, an out-of-bounds write enabling sandboxed code execution via crafted HTML pages.
Google released Chrome 153.0.8010.36/.37 fixing 230 vulnerabilities, including CVE-2026-87491, an out-of-bounds write in the V8 engine that allowed remote code execution inside the sandbox via a crafted HTML page and is confirmed to be exploited in the wild. The flaw was reported on August 6, 2026 by Jihyeon Jeong of Compsec Lab, Seoul National University, who received a $2,500 bug bounty. This is the seventh actively exploited Chrome zero-day of 2026. The update also fixes five critical flaws in WebGL and Cast, plus a high WebPackaging use-after-free (CVE-2026-87639) credited to OpenAI Codex Security.
Google shipped Chrome 153 with 230 fixes, including CVE-2026-87491, a V8 out-of-bounds write zero-day exploited in the wild.
Chrome 153 (153.0.8010.36/.37) rolls out to Windows, Mac, and Linux with 230 security fixes, among the largest patch batches in recent Chrome history. The headline flaw is CVE-2026-87491, a Medium-severity out-of-bounds write in the V8 JavaScript and WebAssembly engine that Google confirmed is exploited in the wild; it was reported by Jihyeon Jeong of Compsec Lab at Seoul National University for a $2,500 bounty. The release also closes five Critical-rated flaws, including CVE-2026-87464, CVE-2026-87488, CVE-2026-87438, CVE-2026-87527, and CVE-2026-87628, mostly use-after-free and out-of-bounds write bugs in WebGL and Cast, plus 43 High-severity issues across ANGLE, PDFium, V8, DevTools, and Payments. Several bugs were surfaced with AI-assisted discovery tools, including OpenAI's Codex Security team, and top bounties reached $5,000 for CVE-2026-87504.
AI-orchestrated campaign exploited PaperCut NG/MF RCE (CVE-2026-81578/82078), compromising 440+ instances at 395 organizations in 48 countries.
GreyNoise tracked a likely Russian-speaking actor using AI (OpenAI Codex harness plus a DeepSeek model) to develop, test, and deploy exploits for PaperCut NG/MF (CVE-2026-81578, CVE-2026-82078) starting 31 August 2026. The actor compromised at least 440 PaperCut instances across 395 organizations in 48 countries, achieving domain admin at 12 victims — fastest time to domain admin was five minutes and a US high school was fully compromised in seven minutes. Attack paths involved LSASS memory and registry secret harvesting, pass-the-hash to domain controllers, noPac attacks, account additions to Domain Admins, and DCSync to exfiltrate full NTDS.DIT credential dumps. Impact scope suggests access development potentially for handoff, with prior PaperCut intrusions historically leading to extortion.
Asana used OpenAI Codex to replace an outdated testing system in two weeks, work estimated at five years for about $12K.
Asana reports using OpenAI's Codex to replace a legacy testing system, completing work originally scoped at five years in roughly two weeks at a cost of about $12,000. OpenAI published the project as a showcase of Codex for large-scale engineering automation. The figures come from the companies' own account and are not independently verified.
Unsafe Reflection RCE in PaperCut NG/MF, Chained with Auth Bypass in Attacks
CVE-2026-82078 is an unsafe dynamic class loading flaw (unsafe reflection, CWE-470) in the database connection utilities of PaperCut NG and PaperCut MF: the software instantiates a database driver class based on a configurable driver name without validating it against an allowlist of approved drivers. An attacker who can manipulate system configuration parameters can point that setting at classes of their choosing, causing the server to execute arbitrary Java bytecode residing on the application classpath in the security context of the PaperCut server process. On its own the issue is rated 9.4 (Critical) with high privileges required, but when chained with the companion authentication bypass CVE-2026-81578 it yields unauthenticated remote code execution on the print-management server. All PaperCut NG and MF deployments are in scope; affected version ranges were not specified in the available data, so administrators should consult PaperCut's advisory for fixed versions. The flaw is confirmed exploited in the wild as a zero-day: it was added to CISA's KEV catalog on 2026-08-31, and public reporting describes an AI-orchestrated campaign that compromised PaperCut servers at roughly 395 organizations (~440 servers), with EPSS currently at 1.7% (76th percentile).
Missing Authentication for Critical Function in PaperCut NG/MF Web Interface
CVE-2026-81578 is an improper access control flaw (CWE-305) in the web management interface of PaperCut MF and PaperCut NG in which administrative requests from unauthenticated remote users trigger backend actions before access validation completes. An attacker can invoke administrative functions without logging in, allowing modification of certain system configurations. When chained with CVE-2026-82078 (unsafe dynamic class loading), the flaw has been used to achieve unauthenticated code execution. Any organization running PaperCut NG/MF, particularly servers whose web management interface is reachable from the internet or untrusted networks, is affected. The vulnerability was added to CISA KEV on 2026-08-31 and is being exploited in the wild as part of an AI-orchestrated campaign that compromised roughly 395–440 organizations.
Actively Exploited Out-of-Bounds Write in Google Chrome V8
CVE-2026-87491 is an out-of-bounds write (CWE-787) in the V8 JavaScript engine in Google Chrome, fixed in Chrome 153.0.8010.36, which Google shipped alongside roughly 230 other security fixes. An attacker can trigger the flaw remotely by luring a user (user interaction required) into opening a crafted HTML page that corrupts memory in V8. Successful exploitation allows the attacker to execute arbitrary code inside the Chrome browser sandbox, which constrains but does not eliminate the impact. All Google Chrome users running versions prior to 153.0.8010.36 are affected; because the flaw resides in V8, CISA tracks it as 'Google Chromium V8', and other Chromium-based browsers may inherit the fix in their own updates. The flaw is being actively exploited in the wild — it is the seventh actively exploited Chrome zero-day of 2026 and was added to CISA's KEV catalog on 2026-09-09 — though no public proof-of-concept is known and ransomware use is unknown.
· Google Chrome (V8 JavaScript engine; tracked by CISA as 'Google Chromium V8') prior to 153.0.8010.36 KEVmass
Use-After-Free in WebGL in Google Chrome Allows Code Execution Outside the Sandbox
CVE-2026-87464 is a use-after-free (CWE-416) in the WebGL component of Google Chrome affecting versions prior to 153.0.8010.36. A remote attacker can trigger it by luring a user to open a crafted HTML page, which corrupts memory in the browser's WebGL rendering path. Successful exploitation allows arbitrary code execution outside the browser sandbox, meaning the attacker escapes Chrome's process isolation and runs code with the privileges of the browser on the host. All Chrome users running an unpatched version before 153.0.8010.36 are affected. As of now there is no public proof-of-concept and this specific flaw is not in CISA KEV, although the Chrome 153 release headlines reference a separate V8 zero-day that was exploited in the wild.
· google chrome all versions prior to 153.0.8010.36mass
Use-After-Free in WebGL in Google Chrome for Android Allows RCE Outside Sandbox
CVE-2026-87488 is a use-after-free (CWE-416) in the WebGL component of Google Chrome on Android, fixed in Chrome 153.0.8010.36. A remote attacker triggers it by luring a user to open a crafted HTML page in a vulnerable Chrome for Android build. Successful exploitation allows the attacker to execute arbitrary code outside the browser's sandbox, meaning code runs beyond the browser's security boundary on the device. All Chrome for Android users running versions prior to 153.0.8010.36 are affected. No public proof-of-concept is known and the flaw is not in CISA's KEV, with EPSS assigning a 0.4% 30-day exploitation probability; note that the same Chrome 153 release fixes 230 issues, including a separate, actively exploited V8 zero-day (code execution inside the sandbox) that should not be confused with this WebGL bug.
· Google Chrome for Android All versions prior to 153.0.8010.36mass
Heap Buffer Overflow in Google Chrome WebGL Enables RCE Outside the Sandbox
CVE-2026-87527 is a buffer overflow (CWE-122) in the WebGL component of Google Chrome that is triggered when a user visits a crafted HTML page, requiring no authentication and no special privileges. Successful exploitation allows a remote attacker to execute arbitrary code outside the browser sandbox, meaning the attacker breaks out of Chrome's core containment boundary — a high-impact outcome reflected in its Critical Chromium severity and 9.6 CVSS score. All users running Google Chrome versions prior to 153.0.8010.36 are affected. As of this analysis there is no public proof of concept, the flaw is not in CISA's KEV, and EPSS estimates only a 0.3% probability of exploitation within 30 days; the zero-day exploited in the wild cited in related headlines is a separate V8 issue also fixed in the Chrome 153 release. Defenders should nonetheless treat this as high priority given the severity, the attack's web-browsing trigger, and the sandbox-escape impact.
· Google Chrome All versions prior to 153.0.8010.36mass
Out-of-Bounds Write in Google Chrome for Android WebGL Enables Sandbox-Escape RCE
CVE-2026-87438 is an out-of-bounds write (CWE-787) in the WebGL component of Google Chrome running on Android. A remote attacker can trigger the flaw by persuading a user to open a crafted HTML page, requiring no privileges and only user interaction. Successful exploitation yields arbitrary code execution outside the browser sandbox, meaning the attacker escapes Chrome's renderer sandbox and compromises the device at a level beyond the web content, with high confidentiality, integrity and availability impact. Users of Chrome on Android prior to 153.0.8010.36 are affected; the fix ships in Chrome 153, a release that includes roughly 230 security fixes. Exploitation of this specific WebGL flaw has not been documented so far (not in CISA KEV, EPSS ~0.4%, no public PoC); the actively exploited zero-day referenced in recent headlines is a separate V8 bug that was patched in the same Chrome 153 release.
· Google Chrome (on Android) All versions prior to 153.0.8010.36; fixed in 153.0.8010.36mass
Use-After-Free in Google Chrome Cast Allows Sandbox-Escaping Code Execution
CVE-2026-87628 is a use-after-free (CWE-416) in the Cast component of Google Chrome, rated Critical by Chromium, that is triggered when the browser processes crafted network traffic sent by an attacker on an adjacent network (e.g., the same LAN segment). A successful attack can allow the adjacent attacker to execute arbitrary code outside the Chrome sandbox, a stronger outcome than typical renderer-only bugs because it escapes Chrome's containment model. All Google Chrome versions prior to 153.0.8010.36 are affected; the flaw is fixed in Chrome 153.0.8010.36, part of the Chrome 153 release that ships 230 security fixes. No public proof-of-concept is known, the bug is not in CISA KEV, and EPSS estimates only a 0.2% chance of exploitation within 30 days, so there is no known exploitation of this specific Cast bug. Note that the actively exploited zero-day in the Chrome 153 headlines is a separate V8 flaw that allows code execution only inside the sandbox, and should not be confused with this outside-the-sandbox Cast issue.
· Google Chrome All versions prior to 153.0.8010.36 (fixed in 153.0.8010.36)mass
Out-of-Bounds Read/Write in Google Chrome V8 Enables In-Sandbox Code Execution
CVE-2026-11645 is an out-of-bounds read and write (CWE-125/CWE-787) in V8, the JavaScript engine used by Google Chrome and Chromium. A remote attacker triggers the flaw by luring a user to a crafted HTML page, where malicious script causes V8 to read and write outside allocated memory buffers. Successful exploitation allows the attacker to execute arbitrary code inside the browser's security sandbox, providing limited privileges within that process rather than full system compromise. All Google Chrome versions prior to 149.0.7827.103 are affected, along with the Chromium V8 component identified by CISA. The flaw is being exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-06-09, and related headlines describe an actively exploited Chrome V8 zero-day, though no public proof-of-concept is known and ransomware use is unconfirmed.
· Google Chrome prior to 149.0.7827.103 · Google Chromium V8 (as shipped in Chrome) prior to the 149.0.7827.103 Chrome release KEVmass
Unsandboxed Git Hook Execution (CWE-427) in OpenAI Codex Desktop
CVE-2026-19590 is a configuration-trust flaw (CWE-427, uncontrolled search path element) in OpenAI Codex Desktop for Windows and macOS, where automated Git operations inside Codex trust the repository's local core.hooksPath setting. It is triggered when a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath at an attacker-controlled directory, causing Codex to execute the attacker's Git hook while processing the repository; an ordinary git clone does not preserve that repository-local configuration, so plain clones are not a delivery path. The hook runs outside Codex's command sandbox, without user approval, and with the user's privileges, giving the attacker the ability to read, modify, or delete the user's files and access other resources available to the user's account. Anyone running an unpatched Codex Desktop on Windows or macOS who opens a repository obtained outside a normal clone (for example an archive or shared folder containing .git/config) is affected. It is scored 7.3 (high, local vector with user interaction), EPSS is 0.1% (1st percentile), it is not in CISA KEV, no public PoC is known, and the issue was publicly documented via ZDI (ZDI-26-648) following a Pwn2Own demonstration.
· OpenAI Codex Desktop for Windows · OpenAI Codex Desktop for macOSmoderate
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.