Appearance
Build dependency security
PushOTA scans production and development dependencies. High and critical runtime findings always block deployment. All raw audit reports are retained by CI.
On 17 November 2026, npm's advisory feed began reporting CVE-2026-112366 in the locked Picomatch build dependencies. No patched upstream release was available.
The local mitigation rejects repeated extglob syntax (+(...) and *(...)) before regex compilation, in both parser entry points. These patterns are not required by our build configuration. This intentionally restricts build glob syntax; it is not a claim that every Picomatch matching feature is preserved. Ordinary wildcards, globstars and brace extension lists remain supported.
The mitigation verifies the original source checksum for every installed copy and fails if a new or modified dependency has not been reviewed. It runs before builds, and regression tests exercise the malicious patterns and ordinary globs.
Scanners still report the affected upstream versions. The CI decision permits only this exact advisory, only in development-only lockfile nodes, only with the verified mitigation installed, and only until 1 December 2026 UTC. Other high or critical findings, incomplete scan evidence, runtime exposure and expiry fail the gate. This temporary decision must be replaced by a tested upstream update when one becomes available; it must not be silently extended.