important3 findings, 20 signals7 min read

VS Code Restricted Mode did not stop workspace-controlled execution; Samsung image decoding and Android Wi-Fi Direct exposed no-interaction code-execution paths.

The first starts when a developer opens an untrusted workspace; the other two start with remotely delivered image data or a nearby Wi-Fi peer.

Priority findings3
01
High
RCE — Developer tools
Confirmed
CVE-2026-81376

An untrusted Visual Studio Code workspace can execute code before Workspace Trust is granted.

Nested settings filtering and workspace-scoped remote-agent configuration opened separate routes through Restricted Mode.

Affects

Visual Studio Code, a cross-platform desktop code editor with Workspace Trust isolation for untrusted repositories.

What it enables

Code execution as the user despite Restricted Mode

Attacker supplies a repository or workspace containing crafted .vscode configurationUser opens it in Visual Studio Code while leaving the workspace untrustedNested-object configuration bypasses restricted-setting filtering, or workspace configuration selects an attacker-controlled remote agent hostRestricted settings or the remote service obtain execution-capable behavior and local-file permissionsAttacker executes code in the context of the Visual Studio Code user
Why this matters

Restricted Mode is the boundary developers rely on when opening unfamiliar repositories without granting them trust.

Detail, proof-of-concept code and 7 sources
Required access

Ability to convince the user to open an attacker-controlled repository or workspace; the user need not grant trust

Affected versions

Visual Studio Code before 1.136.2

The user only has to open the attacker-controlled workspace: crafted nested settings can evade restriction checks, or remote-agent settings can select an attacker service with local-file permissions.

The public fixes add nested-setting regression coverage and remove remote-agent-host selection from workspace-controlled scope.

We do not know whether updating also neutralizes every malicious configuration that an older build already accepted.

Evidence
Microsoft-maintained GitHub advisories describing code execution without granting Workspace TrustPublic fix commits and regression tests for nested restricted settings and remote-agent-host configuration scope
Sources
Share this finding
02
High
Zero-click — Samsung Galaxy
Provisional
CVE-2026-21095

A remotely delivered DNG or JPEG can execute code on affected Samsung Galaxy devices without user interaction.

Both paths begin with heap overflows in Samsung's libimagecodec.quram.so decoders.

Affects

Samsung Mobile Devices using Samsung's proprietary image-decoding library on Android 14 through Android 17.

What it enables

Remote code execution during DNG or JPEG image decoding without user interaction

Attacker remotely supplies a crafted DNG or JPEG through a content-delivery path that reaches the Samsung deviceThe device processes the image with the corresponding libimagecodec.quram.so decoder without user interactionMalformed decoder input causes a heap-based buffer overflowThe overflow permits arbitrary code execution on the device
Why this matters

The Samsung records require neither privileges nor user interaction, moving these decoder bugs from memory corruption to a passive remote code-execution capability.

Detail, proof-of-concept code and 4 sources
Required access

Network delivery through a path that causes the device to process a crafted image; Samsung's CNA records require no privileges or user interaction but leave an additional attack requirement unspecified.

Affected versions

Samsung Mobile Devices before SMR Sep-2026 Release 1 running Android 14, Samsung Mobile Devices before SMR Sep-2026 Release 1 running Android 15, Samsung Mobile Devices before SMR Sep-2026 Release 1 running Android 16, Samsung Mobile Devices before SMR Sep-2026 Release 1 running Android 17

An attacker sends crafted image data through a path that causes the device to invoke the DNG or JPEG decoder; the resulting heap overflow permits code execution during processing.

Samsung says the flaws were addressed in a shipped maintenance release.

We still do not know the concrete delivery transport or the additional attack requirement recorded by Samsung, and no public trigger artifact was identified.

Evidence
Samsung's bulletin identifies both heap overflows, affected Android versions, remote code execution and the shipped maintenance releaseSamsung-authored CNA records classify both as network-reachable, unauthenticated and requiring no user interaction, with attack requirements presentNo public trigger artifact or concrete delivery transport was found
Share this finding
03
High
Wi-Fi — Android
Confirmed
CVE-2026-28662

A nearby Wi-Fi Direct peer can execute code in Android's Wi-Fi service without user interaction.

An oversized PBMA cookie length drives a heap write beyond the allocation in P2P2 bootstrap processing.

Affects

Android smartphones and other Android devices using the platform wpa_supplicant Wi-Fi Direct implementation.

What it enables

Adjacent remote code execution in the Android Wi-Fi service

Enter Wi-Fi radio range of an affected Android device.Answer its P2P2 bootstrap Provision Discovery Request with an oversized cookie length in the PBMA attribute.wpa_supplicant copies beyond its heap buffer.The Android bulletin classifies the resulting capability as proximal remote code execution without user interaction.
Why this matters

This crosses directly from an unauthenticated radio peer into Android's Wi-Fi service without asking the user to approve a connection or take another action.

Detail and 2 sources
Required access

Wi-Fi radio range and the ability to answer a P2P2 bootstrap Provision Discovery Request from the target

Affected versions

Android 16, Android 16 QPR2, Android 17

The attacker enters Wi-Fi range, answers the target's P2P2 bootstrap Provision Discovery Request with an oversized cookie length, and causes wpa_supplicant to copy beyond its heap buffer.

The AOSP change and Android bulletin connect that attacker-controlled write to proximal remote code execution requiring no privileges or interaction.

The published fix closes this oversized-cookie path.

Evidence
The AOSP commit identifies a malicious Wi-Fi Direct peer, the oversized attacker-controlled cookie length, and the heap overflow.Google's Android bulletin and CVE classification identify CVE-2026-28662 as remote code execution requiring neither extra privileges nor user interaction.
Share this finding
Signals20
important · Research — Agentic payments

Merchant prose can redirect an AP2 agent across both credential and purchase-intent boundaries.

Affects

Agent Payments Protocol (AP2), a protocol and reference implementation for agent-mediated shopping and payments.

A merchant can place instructions or false claims in product text that the agent consumes before it creates the signed checkout artifacts.

Detail and 4 sources

The reported tests produced cross-user credential retrieval, mismatched carts and more expensive purchases across 17 Google models, three frameworks and Google's consumer assistant.

The public benchmark includes reproduction material, and no fix is identified.

This stays secondary because current production adoption and reach are not established.

important · Wi-Fi — RouterOS

RouterOS accepted forged TLS certificate chains without a trusted private key.

Affects

MikroTik RouterOS, the operating system used by MikroTik routers and wireless network appliances.

Malformed RSA/PKCS#1 v1.5 signatures and RouterOS's trusted exponent-three root let an attacker construct a forged intermediate and issue a certificate for the requested hostname.

Detail and 3 sources

CERT Polska confirmed the behavior on real systems with repetition and negative controls.

The attacker still needs destination control or an on-path redirection position.

Fixed releases close the path, but pre-fix images remain accepted and some affected hardware is already end of life.

important · RCE — Developer tools

Opening a malicious folder in OpenAI Codex can execute code as the developer user.

Affects

OpenAI Codex, an AI coding agent running on developer workstations.

The folder supplies Git-command arguments containing control sequences that Codex does not sufficiently neutralize before parsing.

Detail and 1 source

The coordinated advisory identifies current-user code execution and says the flaw is patched.

important · Physical — Windows

Attacker-controlled storage can reach Windows kernel code execution through Spaceport.sys.

Affects

Microsoft Windows 10, Windows 11, and Windows Server, desktop and server operating systems.

Physical access is sufficient to present input that reaches a heap-based buffer overflow in the storage driver; no account or user interaction is recorded.

Detail and 2 sources

We do not know the storage transport, malformed structure, or whether the path works at the lock screen or before sign-in.

The affected population includes end-of-life Windows hardware.

Chain to watch
Present attacker-controlled storage to an affected Windows machineTrigger the Spaceport.sys heap overflowReach kernel-context code executionThe storage transport, malformed input and lock-screen or pre-sign-in reach are unknown.
Unverified chainDiff Spaceport.sys across the September fixed-build boundaries, identify the changed parser, and exercise it with representative attached storage.
important · Edge — Browser chain

BlueMoon composes a clicked browser link into Windows broker command execution.

Affects

Google Chrome and Chromium-based browsers on selected Windows 10, Windows 11 and Windows Server builds targeted by the BlueMoon exploit kit.

Two V8 flaws provide renderer execution, an ALPC/WNF exploit changes token rights, and injected broker code downloads and executes the operator-selected payload.

Detail and 5 sources

Proofpoint observed four threat clusters deploy the complete chain, and Google confirmed exploitation of the V8 components in the wild.

Today's change is evidence that the previously tracked browser bugs were operationally composed through the Windows sandbox boundary; Google and Microsoft have shipped fixes.

important · Physical — Windows

Three Windows USB and SCSI flaws let an attached device elevate privileges without login or consent.

Affects

Microsoft Windows 10, Windows 11, and Windows Server, desktop and server operating systems with USB and SCSI storage support.

The recorded primitives are two out-of-bounds reads and an untrusted-pointer dereference in kernel-mode storage and hub drivers.

Detail and 6 sources

Microsoft does not disclose the triggering descriptors or commands, or the precise privileges obtained.

Affected systems include end-of-life hardware.

Chain to watch
Attach or present a malicious USB or SCSI-class deviceReach an affected kernel driver with device-controlled inputObtain elevated Windows privilegesThe triggering device structures and resulting privilege level are unknown.
Unverified chainDiff the September USBSTOR, USB hub and SCSI class driver binaries, then fuzz the changed paths with instrumented USB and virtual SCSI hardware.
important · Mobile — Chrome

An exploited V8 write gives crafted pages native execution inside Chrome for Android's renderer.

Affects

Chrome for Android, Google’s mobile web browser running on Android devices.

The victim must load attacker-controlled HTML, which triggers the V8 out-of-bounds write and reaches code execution inside the renderer sandbox.

Detail and 3 sources

Chrome for Android 153.0.8010.36 contains the corresponding fix.

Chain to watch
Load crafted HTML in Chrome for AndroidTrigger the V8 out-of-bounds writeExecute code inside the renderer sandboxNo Android-applicable sandbox escape has been established.
Unverified chainIdentify the observed exploitation chain and determine whether it contained an Android sandbox escape.

The major Android containment boundary still holds in the established chain; we do not know whether observed exploitation included an Android-applicable escape.

important · Edge — GitLab

Attackers are exploiting GitLab's unauthenticated commit endpoint to read arbitrary server files.

Affects

GitLab Community Edition and Enterprise Edition, self-managed source-code and CI/CD servers.

A crafted commit request reaches File.read without authentication, and malformed percent encoding reflects the selected file through error handling.

Detail and 4 sources
important · Boot chain — Windows

Windows Boot Manager has a newly recorded physical privilege-elevation path, but its trigger is undisclosed.

Affects

Microsoft Windows 10, Windows 11, and Windows Server systems using Windows Boot Manager.

Microsoft records physical access, no prior privileges and no user interaction, but supplies no CWE or technical path.

Detail and 2 sources

We do not know the resulting privilege, required boot configuration, or relationship to Secure Boot and BitLocker.

Chain to watch
Physically possess an affected Windows deviceReach an undisclosed Boot Manager validation or authorization failureObtain elevated privilegesThe trigger, privilege transition and dependence on Secure Boot or BitLocker remain unknown.
Unverified chainDiff bootmgfw.efi and related boot binaries across the September build boundary, then test candidate paths with Secure Boot and BitLocker enabled.

Fixed builds exist, but the changed validation or authorization logic has not been established.

important · Firmware — MediaTek

Two MediaTek decoder heap writes are described as local elevation paths across 54 chipsets.

Affects

MediaTek video-decoder components in Android and embedded devices using the listed MediaTek chipsets.

An unprivileged local process must reach an unpublished video-ingestion route before either missing bounds check produces its heap out-of-bounds write.

Detail and 1 source

We do not know whether the writes are controllable into code execution or which final privilege context they cross.

Chain to watch
Obtain unprivileged local execution on an affected deviceReach the MediaTek video-decoder input pathTrigger a heap out-of-bounds write and attempt privilege escalationControllability and the final Android or firmware privilege context are unknown.
Unverified chainReproduce each malformed input on an OEM build while recording the decoder process, SELinux domain and resulting memory control.

MediaTek announced a patch and identified the chipset scope.

important · Edge — SonicWall

Public Metasploit code turns the SMA1000 WorkPlace service into a root session.

Affects

SonicWall Secure Mobile Access 1000 Series, internet-facing enterprise remote-access gateways.

An unauthenticated HTTPS request reaches loopback CouchDB, enables its Erlang query server, derives a DMI-based control credential and uses sed injection to execute a root command.

Detail and 6 sources
important · Firmware — ThinOS

Unauthenticated network input can execute commands or code on Dell ThinOS 10 clients.

Affects

Dell ThinOS 10, the embedded operating system deployed across Dell thin-client endpoint fleets.

A reachable ThinOS component passes unauthenticated attacker input into an operating-system command or application-code execution path.

Detail and 2 sources
important · Wi-Fi — RouterOS

Unauthenticated WebFig requests can disclose root-owned RouterOS files and stored credentials.

Affects

MikroTik RouterOS, the operating system used by MikroTik routers and wireless network appliances.

Allocator shaping leaves a stale principal pointer in a new /jsproxy session, after which parent-directory components escape the encrypted-URI file namespace.

Detail and 3 sources

Today's change establishes that the reachable scope includes root-owned files and credential-containing configuration stores; MikroTik has shipped fixed releases.

important · Privilege — Windows

Incorrect Windows MIDI Services permissions let a low-privilege process execute as SYSTEM.

Affects

Windows MIDI Services, the operating-system MIDI stack on affected Windows installations.

An existing low-privilege process can influence an incorrectly permissioned service resource and obtain SYSTEM-context command execution.

Detail and 1 source

Microsoft has published fixed Windows builds.

important · Privilege — Android

Any Android app can become root on kernels using affected FolkPatch releases.

Affects

FolkPatch, an Android rooting project that patches device kernels with a custom KernelPatch fork.

The app invokes FolkPatch's retained supercall interface with the public hardcoded SuperKey "su," and the kernel executes its requested command as root.

Detail and 4 sources
important · Edge — Printing

A remotely submitted raster job can execute code in a PAPPL print service.

Affects

PAPPL, a C printing-application framework used to expose IPP printing services on Unix-like systems.

On a listener configured for remote jobs, attacker-controlled cupsWidth drives raster loops beyond the heap line buffer allocated for the output width.

Detail and 2 sources
important · Edge — Akana

An authentication-filter mismatch exposes Akana Policy Manager's script evaluator to unauthenticated callers.

Affects

Akana API Platform Policy Manager, an enterprise API-management console operated on customer infrastructure.

A crafted path is interpreted differently by the authentication filter and servlet dispatcher, allowing the request to reach unsandboxed script evaluation.

Detail and 4 sources
important · RCE — Build workers

A crafted gem can execute publisher-controlled code on RubyDoc.info documentation workers.

Affects

RubyDoc.info, the hosted service that automatically builds documentation for packages published through RubyGems.

A publisher places a Ruby payload behind a gem-controlled .yardopts file and requests documentation generation, causing the worker to evaluate the package's build configuration.

Detail and 2 sources

The September 11 report identified more than one hundred public packages using this execution path and preserved payload examples.

RubyDoc.info's current patch state is unknown.

important · Bluetooth — Firmware

A malformed channel map can transiently disable Qualcomm Bluetooth controllers.

Affects

Qualcomm Bluetooth controller firmware spanning mobile, compute, audio, fixed-wireless, XR and networking chipsets.

A nearby device supplies a channel map with too few used channels while adaptive frequency hopping is fully enabled, triggering a controller buffer over-read.

Detail and 1 source

The established result is temporary Bluetooth unavailability, not code execution or persistent compromise.

Qualcomm shared corrected proprietary code with customers, but end-user OEM firmware availability is not established.

important · Privilege — Defender

ShieldCrash's released code does not establish its claimed post-fix SYSTEM file read.

Affects

Microsoft Defender Malware Protection Engine, the built-in antimalware engine on supported Windows clients and servers.

The repository combines Cloud Filter hydration, Object Manager links and an NTFS reparse point and claims arbitrary file read as SYSTEM with a path toward SYSTEM execution.

Detail and 4 sources

An independent reproduction reached the redirect pipeline, but SAM, SECURITY and ELAM reads failed before protected-file bytes were returned.

Chain to watch
Register a Cloud Filter synchronization root and seed a file for Defender remediationRace Object Manager links and an NTFS reparse point during privileged handlingAttempt to substitute and return an attacker-selected protected fileThe public code has not returned bytes from an attacker-selected protected file.
Unverified chainCorrect the sharing-violation and reparse timing failure, verify protected-file bytes on engine 1.1.26080.3, and only then test a controlled SYSTEM token transition.

The claimed post-fix capability remains unestablished until the code returns bytes from a protected target and demonstrates any resulting SYSTEM transition.

Also noted0

No additional findings today.

What was checked · 1 quiet
Boot chain & TPMQuiet

The Windows Boot Manager privilege path remains opaque; the separate UEFI-shell, TPM and U-Boot material did not establish a new validation bypass.

Get it by email

The same brief, every morning. One email a day, nothing else.

fullchain.sh follows the day’s disclosures from bug to shell — what each one enables, what it links to, and where the fix left the primitive in place.

Every finding here carries a source that was checked before it published. If something is wrong, write to admin@fullchain.sh — corrections are published on the day they affect.

Sunday, September 13, 2026