critical

CVE

CVE-2026-110697, CVE-2026-123710, CVE-2026-61619, CVE-2026-62971, CVE-2026-64855, CVE-2026-65820, CVE-2026-123374, CVE-2026-105153, CVE-2026-118411, CVE-2026-105152, CVE-2026-105154, CVE-2026-71395, CVE-2026-44929, CVE-2026-49236, CVE-2026-89326, CVE-2026-90993, CVE-2026-111792, CVE-2026-40853, CVE-2026-126627, CVE-2026-124686, CVE-2026-124687, CVE-2026-124690, CVE-2026-106152, CVE-2026-106156, CVE-2026-106137, CVE-2026-111024, CVE-2026-111000, CVE-2026-102589, CVE-2026-107509, CVE-2026-122043, CVE-2026-123747, CVE-2026-117373, CVE-2026-64858, CVE-2026-115819, CVE-2026-100290

CWE

CWE-287, CWE-89, CWE-1333, CWE-436, CWE-295, CWE-502, CWE-611, CWE-918, CWE-94, CWE-78, CWE-22

Affected Surface

  • Red Hat Quay container registry deployments (`CVE-2026-123710` CVSS 9.8 Critical unauthenticated signing-key installation and `CVE-2026-110697` CVSS 9.9 Critical cross-tenant robot token disclosure via SQL `LIKE` `_` wildcard)
  • OWASP ModSecurity Core Rule Set (`coreruleset/coreruleset`) versions `< 3.3.10`, `>= 4.0.0, < 4.25.1`, and `4.26.0`..`4.27.0` (`CVE-2026-61619` / `GHSA-f5qm-3h4p-8qhg` CVSS 8.8 High PCRE2 match-limit RCE rule bypass and `CVE-2026-62971` / `GHSA-6jp8-c2w2-x7wr` CVSS 7.2 High `XML:/*` attribute WAF bypass, fixed in `3.3.10`, `4.25.1`, and `4.28.0`)
  • PyPI `soapbar` `< 0.13.0` (`CVE-2026-64855` / `GHSA-859w-52fx-hcm6`, CVSS 8.2 High), `aeon` `< 1.5.0` (`CVE-2026-65820` / `GHSA-mhg2-mc45-wrjr`, CVSS 8.7 High), and Meta `fairchem-core` (`FAIRChem`) & `fairseq` / `fairseq2` (`ZDI-26-924` through `ZDI-26-953`, 30 unpatched 0-day RCE advisories, CVSS 7.8 High)
  • Maven / Java Apache Roller `4.0` through `6.1.6` (`CVE-2026-123374`, `CVE-2026-105153`, `CVE-2026-118411`, plus 12 more CVEs fixed in `6.1.7`), Apache XML Graphics Batik `<= 1.19` (`CVE-2026-44929`, `CVE-2026-49236`, `CVE-2026-89326`, `CVE-2026-90993`, `CVE-2026-111792`, `CVE-2026-40853`, fixed in `1.20`), and Apache XML Graphics FOP `<= 2.11` (`CVE-2026-71395` CWE-502 unsafe deserialization and `CVE-2026-126627`, fixed in `2.12`)
  • GNU Emacs `31.1` (`.dir-locals.el` `auto-mode-alist` arbitrary code execution, `debbugs#82213`), GNU C Library `glibc` `2.2` to `2.44` (`GLIBC-SA-2026-0027` / `CVE-2026-115819` and `GLIBC-SA-2026-0028` / `CVE-2026-100290`), Progress Kendo UI for jQuery `< 2026.4.1110` / `< 2026.4.1111` (`CVE-2026-124686`..`124694`), Telerik UI for ASP.NET Core/MVC `< 2026.3.1015` & Report Server `< 12.3.26.1110` (`CVE-2026-106152`, `106156`, `106137`), Grafana (`CVE-2026-111024`, `111000`, `102589`, `107509`), `repmgr` `4.0.0`..`5.5.0` (`CVE-2026-122043`, fixed in `5.5.1`), `pappl-retrofit` `< 1.0b3` (`CVE-2026-123747` CVSS 9.6), Janus WebRTC `< 1.4.2` (`CVE-2026-117373`), and `vulnerability-operator` `< 0.28.16` (`CVE-2026-64858`)

TL;DR

On 11 November 2026 (12:00 to 18:19 UTC), NVD, oss-security, the GitHub Advisory Database, and the Zero Day Initiative published a second wave of disclosures affecting container registries, web application firewalls, Python and Java libraries, developer editors, and machine-learning toolkits:

  1. Red Hat Quay container registry critical authentication and cross-tenant token leaks (CVE-2026-123710, CVSS 9.8 Critical; CVE-2026-110697, CVSS 9.9 Critical):
    • Unauthenticated signing-key installation (CVE-2026-123710): An unauthenticated client can request an anonymous registry bearer token with a caller-controlled aud (audience) claim, present that token to Quay’s service-key rotation endpoint, and register its own approved signing key with no expiration date. Quay then accepts registry tokens signed by the attacker’s key for pull and push access across any private repository.
    • Cross-tenant robot token theft via unescaped SQL LIKE wildcard (CVE-2026-110697): When listing robot accounts for a namespace, Quay constructed a SQL LIKE pattern from the caller’s namespace name without escaping _ or %. Because _ matches any single character in SQL LIKE clauses, an authenticated user who registers a namespace such as a_b retrieves robot accounts and their decrypted authentication tokens belonging to other tenants (such as aab, acb, or adb).
  2. OWASP ModSecurity Core Rule Set (CRS) 3.3.10, 4.25.1, and 4.28.0 fix two WAF detection bypasses (CVE-2026-61619 / GHSA-f5qm-3h4p-8qhg, CVSS 8.8 High; CVE-2026-62971 / GHSA-6jp8-c2w2-x7wr, CVSS 7.2 High):
    • Single-request PCRE2 match-limit bypass across 12 Unix RCE rules (CVE-2026-61619, commit 4665b6d7a79a): A shared command-prefix pattern in CRS v4 (932100 to 932320) and v3.3 contained a duplicated |\$.*|\$.* branch and nested \s* quantifiers. A single unauthenticated HTTP request drives PCRE2 past its backtracking limit, causing ModSecurity’s @rx operator to abort with a match error and fail open (bypassing Unix RCE inspection while burning CPU).
    • XML attribute blindness across ~159 rules (CVE-2026-62971, commit 275d7616f1ce): Rules in families 921 (protocol), 930 (LFI), 931 (RFI), 932 (RCE), 933 (PHP), 934 (generic), 941 (XSS), 942 (SQLi), and 943 (session fixation) inspected XML request bodies using only XML:/* (which selects element text nodes) and omitted XML://@* (attribute values), allowing SQLi, XSS, LFI, or RCE payloads placed inside XML attributes (<item filter="' OR 1=1 --"/>) to pass through CRS at every paranoia level (PL1 to PL4).
  3. Python soapbar 0.13.0 (CVE-2026-64855, CVSS 8.2 High), aeon 1.5.0 (CVE-2026-65820, CVSS 8.7 High), and 30 ZDI 0-day RCE advisories in Meta FAIRChem and fairseq / fairseq2 (ZDI-26-924 to ZDI-26-953, CVSS 7.8 High): In soapbar < 0.13.0, verify_envelope_bsp() verified WS-Security SOAP signatures against the X.509 certificate embedded inside the untrusted message’s wsse:BinarySecurityToken without checking any CA chain or pinned certificate (PR #71). Meanwhile, ZDI published 30 unpatched 0-day RCE advisories across Meta’s fairchem-core (ZDI-26-945 to 953) and archived fairseq / fairseq2 (ZDI-26-924 to 944) caused by unsafe torch.load / pickle checkpoint deserialization, numpy.load(..., allow_pickle=True) on .npz submissions, and eval() inside YAML config and manifest parsers.
  4. Apache Roller 6.1.7 (15 CVEs), Apache Batik 1.20 & FOP 2.12 (8 CVEs), GNU Emacs 31.1 (.dir-locals.el RCE), GNU C Library (GLIBC-SA-2026-0027 / 0028), Progress Kendo UI 2026.4.1111 (CVE-2026-124686..124694) & Telerik (CVE-2026-106152, 106156, 106137), Grafana (CVE-2026-111024, 111000, 102589, 107509), repmgr 5.5.1 (CVE-2026-122043), pappl-retrofit 1.0b3 (CVE-2026-123747, CVSS 9.6), and Janus WebRTC 1.4.2 (CVE-2026-117373).

What to do now: Apply Red Hat Quay security updates and audit service keys and _-named namespaces; upgrade OWASP CRS to 3.3.10, 4.25.1, or 4.28.0; upgrade soapbar to >= 0.13.0 (and pass trusted_certs=[...] or ca_certs=[...]), Apache Roller to >= 6.1.7, Apache Batik to >= 1.20, Apache FOP to >= 2.12, Kendo UI for jQuery to >= 2026.4.1111, Telerik UI for ASP.NET Core/MVC to >= 2026.3.1015 and Report Server to >= 12.3.26.1110, repmgr to >= 5.5.1 (and remove double quotes around %a/%c/%d in repmgr.conf), pappl-retrofit to >= 1.0b3, and Janus WebRTC to >= 1.4.2; and apply Stefan Monnier’s lisp/files.el patch on GNU Emacs 31.1.

Affected packages and components

EcosystemPackage / ProductCVE / Advisory IDsSeverityAffected versionsFixed version
Container RegistryRed Hat Quay (quay/quay)CVE-2026-110697, CVE-2026-123710CVSS 9.9 / 9.8 CriticalPrior to Nov 2026 Quay patchesRed Hat Quay security update
ModSecurity / WAFOWASP Core Rule Set (coreruleset/coreruleset)CVE-2026-61619 (GHSA-f5qm-3h4p-8qhg), CVE-2026-62971 (GHSA-6jp8-c2w2-x7wr)CVSS 8.8 / 7.2 High< 3.3.10; >= 4.0.0, < 4.25.1; 4.26.0..4.27.03.3.10, 4.25.1, 4.28.0
PyPIsoapbar (hitoshyamamoto/soapbar)CVE-2026-64855 (GHSA-859w-52fx-hcm6)CVSS 8.2 High< 0.13.00.13.0
PyPI / GitHub Actionsaeon (aeon-toolkit/aeon)CVE-2026-65820 (GHSA-mhg2-mc45-wrjr)CVSS 8.7 High< 1.5.01.5.0 (commit 99261e1355c8)
PyPI / AIMeta fairchem-core (FAIRChem), fairseq, fairseq2ZDI-26-924 through ZDI-26-953 (30 0-days)CVSS 7.8 High (RCE)All current versions (fairseq archived)0-day (unpatched; never load untrusted checkpoints/YAML)
Maven / JavaApache Roller (org.apache.roller)CVE-2026-123374, CVE-2026-105153, CVE-2026-118411, CVE-2026-105152, CVE-2026-105154, plus 10 CVEsCritical / High / Medium4.0 through 6.1.66.1.7
Maven / JavaApache XML Graphics Batik & FOPBatik: CVE-2026-44929, 49236, 89326, 90993, 111792, 40853; FOP: CVE-2026-71395, 126627High / ModerateBatik <= 1.19; FOP <= 2.11Batik 1.20; FOP 2.12
JavaScript / .NETProgress Kendo UI for jQuery, Telerik UI for ASP.NET Core/MVC, Telerik Report ServerCVE-2026-124686..124694; CVE-2026-106152, 106156, 106137, 106133CVSS 8.8 / 8.6 / 7.1 HighKendo UI < 2026.4.1111; Telerik UI <= 2026.3.811; Report Server < 12.3.26.1110Kendo UI 2026.4.1111; Telerik UI 2026.3.1015; Report Server 12.3.26.1110
Editor / LinuxGNU Emacs 31.1, GNU C Library (glibc), pappl-retrofit, repmgr, Janus WebRTC, GrafanaEmacs debbugs#82213; CVE-2026-115819, 100290; CVE-2026-123747 (CVSS 9.6); CVE-2026-122043; CVE-2026-117373; CVE-2026-111024, 111000, 102589CVSS 9.6 Critical to 3.7 LowEmacs 31.1; glibc <= 2.44; pappl-retrofit < 1.0b3; repmgr <= 5.5.0; Janus 1.2.3..1.4.0Emacs 31.2 (files.el patch); pappl-retrofit 1.0b3; repmgr 5.5.1; Janus 1.4.2

Technical analysis

1. OWASP CRS 3.3.10 / 4.25.1 / 4.28.0: PCRE2 backtracking fail-open (CVE-2026-61619) and XML attribute blindness (CVE-2026-62971)

Both OWASP Core Rule Set advisories published on 11 November allow an attacker to slip exploit payloads past ModSecurity-compatible WAFs (including Envoy, Nginx, Apache, and cloud WAF engines running CRS):

  1. PCRE2 match-limit exhaustion in Unix RCE rules (CVE-2026-61619 / GHSA-f5qm-3h4p-8qhg, CVSS 8.8 High): Twelve Unix command-injection rules in CRS v4 (932100 through 932320 in rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf) and four rules in CRS v3.3 share a command-prefix assembly regex that contained a duplicated |\$.*|\$.* alternation inside \w+=(?:[^\s]*|\$.*|\$.*|<.*|>.*|\'.*\'|\".*\")\s+ alongside an ungrouped {|\s*\(\s*:
    --- a/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf
    +++ b/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf
    @@ -89,7 +89,7 @@
    -# SecRule REQUEST_COOKIES|!REQUEST_COOKIES:/__utm/|REQUEST_COOKIES_NAMES|ARGS_NAMES|ARGS|XML:/* "@rx (?:;|\{|\||\|\||&|&&|\n|\r|\$\(|\$\(\(|`|\${|<\(|>\(|\(\s*\))\s*(?:{|\s*\(\s*|\w+=(?:[^\s]*|\$.*|\$.*|<.*|>.*|\'.*\'|\".*\")\s+|!\s*|\$)*\s*(?:'|\")*(?:[\?\*\[\]\(\)\-\|+\w'\"\./\\\\]+/)?[\\\\'\"]*
    +# SecRule REQUEST_COOKIES|!REQUEST_COOKIES:/__utm/|REQUEST_COOKIES_NAMES|ARGS_NAMES|ARGS|XML:/* "@rx (?:;|\{|\||\|\||&|&&|\n|\r|\$\(|\$\(\(|`|\${|<\(|>\(|\(\s*\))\s*(?:{\s*|\(\s*|\w+=(?:[^\s]*|\$.*|<.*|>.*|\'.*\'|\".*\")\s+|!\s*|\$\s*)*\s*(?:'|\")*(?:[\?\*\[\]\(\)\-\|+\w'\"\./\\\\]+/)?[\\\\'\"]*
    When an attacker sends a single request containing a command prefix followed by repeated variable-assignment tokens (such as ;a=$...), PCRE2 hits its internal match-backtracking limit (MSC_PCRE_LIMITS_EXCEEDED). Because @rx returns non-match when PCRE2 aborts on the limit, the attacker can prepend a backtracking prefix to a real Unix command-injection payload and bypass all 12 RCE rules.
  2. Missing XML://@* target across ~159 rules (CVE-2026-62971 / GHSA-6jp8-c2w2-x7wr, CVSS 7.2 High): In ModSecurity, XML:/* evaluates the XPath expression /* (element text nodes only), whereas XML attribute values require XML://@*. Except for REQUEST-944-APPLICATION-ATTACK-JAVA.conf, every other CRS rule file (921 through 943) listed XML:/* without XML://@* (commit 275d7616f1ce). Any SQLi, XSS, LFI, RFI, PHP, or RCE payload placed inside an XML attribute bypassed CRS inspection completely.

2. Red Hat Quay (CVE-2026-123710, CVE-2026-110697), Python soapbar 0.13.0 (CVE-2026-64855), and Apache Roller 6.1.7 (CVE-2026-123374, CVE-2026-105153)

  • Red Hat Quay (CVE-2026-123710 CVSS 9.8 and CVE-2026-110697 CVSS 9.9): In CVE-2026-123710, Quay’s anonymous token endpoint allowed the caller to specify an arbitrary aud (audience) string, and the internal service-key rotation endpoint accepted a bearer token carrying that audience as proof of authorization to register a new cluster signing key with expiration: null. In CVE-2026-110697, Quay queried robot accounts belonging to <namespace>+* using a SQL LIKE filter without escaping SQL wildcard characters (_ and %), allowing a user who created a namespace with _ to read robot credentials across matching tenant namespaces.
  • Python soapbar < 0.13.0 (CVE-2026-64855 / GHSA-859w-52fx-hcm6): In src/soapbar/core/wssecurity.py (PR #71), verify_envelope_bsp(envelope) extracted the signer’s X.509 certificate from the inbound SOAP message’s <wsse:BinarySecurityToken>, checked only not_valid_before and not_valid_after, and verified the XML-DSig signature against that same certificate. Any attacker who generated a self-signed certificate and signed a forged SOAP envelope passed verify_envelope_bsp(). Version 0.13.0 adds _validate_bsp_cert_trust() and raises XmlSecurityError unless the caller supplies trusted_certs=[...] or ca_certs=[...].
  • Apache Roller 6.1.7 (CVE-2026-123374, CVE-2026-105153, CVE-2026-118411, CVE-2026-105152, CVE-2026-105154) and Apache Batik 1.20 / FOP 2.12 (CVE-2026-71395, CVE-2026-44929, CVE-2026-49236, CVE-2026-89326): When Apache Roller sent an outbound weblog update ping, its Apache XML-RPC client enabled extensions that deserialized raw Java <ex:serializable> objects from the ping target’s HTTP response (CVE-2026-123374, fixed in PR #236), while its AtomPub endpoint parsed XML entries with external DTDs/entities enabled before checking whether AtomPub was enabled or whether the caller had weblog permissions (CVE-2026-105153). In Apache FOP <= 2.11, hyphenation pattern loading deserialized Java objects via ObjectInputStream (CVE-2026-71395), while Batik <= 1.19 allowed color-profile xml:base attributes and cross-protocol URLs to bypass external-resource same-origin checks (CVE-2026-49236, CVE-2026-89326).

3. GNU Emacs 31.1 .dir-locals.el RCE (debbugs#82213), pappl-retrofit 1.0b3 (CVE-2026-123747), Kendo UI (CVE-2026-124686), repmgr 5.5.1 (CVE-2026-122043), and 30 Meta FAIRChem / fairseq 0-days (ZDI-26-924..953)

  • GNU Emacs 31.1 .dir-locals.el arbitrary code execution (oss-security 2026/11/11/7, debbugs#82213): In lisp/files.el, set-auto-mode--apply-alist checked (set-auto-mode--dir-local-valid-p mode) only on the final mode returned by set-auto-mode--find-matching-alist-entry. However, when .dir-locals.el configured an auto-mode-alist entry of the two-pass form (REGEXP FUNCTION t) (where the trailing t tells Emacs to strip the matched suffix and keep searching the alist), the loop in set-auto-mode--find-matching-alist-entry immediately executed (set-auto-mode-0 mode t) for the earlier entry before set-auto-mode--dir-local-valid-p ever ran:
    --- a/lisp/files.el
    +++ b/lisp/files.el
    @@ -3580,9 +3580,6 @@
    -        (when newmode
    -          (when mode
    -            (set-auto-mode-0 mode t))
    -          (setq mode newmode))
    +          (when newmode
    +            (if (and dir-local
    +                     (not (set-auto-mode--dir-local-valid-p mode)))
    +                (message "Ignoring invalid mode `%S'" mode)
    +              (set-auto-mode-0 mode keep-mode-if-same)
    Opening any file inside a cloned repository containing a crafted .dir-locals.el in Emacs 31.1 executed arbitrary Emacs Lisp functions without prompting (Emacs 30.2 is unaffected).
  • pappl-retrofit < 1.0b3 (CVE-2026-123747 / GHSA-wxj6-x3wg-4vmc, CVSS 9.6 Critical, commit c65a28f5ea17) and repmgr < 5.5.1 (CVE-2026-122043): In pappl-retrofit/web-interface.c, _prSystemWebAddPPD() concatenated the uploaded filename and form-deleted PPD name directly onto global_data->user_ppd_dir (snprintf(destpath, ..., "%s/%s", ...)), allowing ../../ traversal to write or delete arbitrary files on the system. In repmgr 4.0.0 to 5.5.0, event_notification_command and failover_validation_command substituted %a (node name) and %c (conninfo) from repmgr.nodes into sh -c without escaping, and %d only escaped ", allowing $(...) command substitution inside double quotes.
  • Progress Kendo UI < 2026.4.1111 (CVE-2026-124686..124694) and 30 Meta FAIRChem / fairseq 0-days (ZDI-26-924 to ZDI-26-953): In Kendo UI for jQuery, kendo.init() fell back to compiling data-* attribute strings with new Function(...) whenever JSON.parse() failed (CVE-2026-124686), and sanitizeSvgContent() parsed custom icon SVG strings into a live DOM before stripping unsafe elements (CVE-2026-124690). Across Meta’s fairchem-core (ZDI-26-945 to 953) and archived fairseq / fairseq2 (ZDI-26-924 to 944), ZDI disclosed 30 unpatched 0-days where checkpoint loaders (load_inference_model, load_model_and_weights_from_checkpoint, migrate_checkpoint, convert_fine_tune_checkpoint, MLIPPredictUnit, load_tasks, FileCheckpointManager._load_state_dict), .npz submission helpers (make_submission_file, make_challenge_submission_file), and YAML/manifest parsers invoke torch.load(..., weights_only=False), numpy.load(..., allow_pickle=True), or eval() on untrusted model or configuration files.

Detection and remediation

# 1. Check OWASP CRS, Python soapbar/aeon/fairchem/fairseq, and Java Roller/Batik/FOP versions
pip show soapbar aeon fairchem-core fairseq fairseq2 2>/dev/null || true
rg -n 'coreruleset|soapbar|aeon|fairchem|fairseq|org\.apache\.roller|batik-|fop-core|kendo-ui' \
  pyproject.toml requirements*.txt uv.lock pom.xml build.gradle* package.json 2>/dev/null

# 2. Check Red Hat Quay namespaces for '_' wildcards and repmgr.conf for %a/%c/%d placeholders
rg -n 'event_notification_command|failover_validation_command' /etc/repmgr*.conf /var/lib/pgsql/*/repmgr*.conf 2>/dev/null || true
  1. Patch Red Hat Quay and audit service keys and robot tokens: Apply Red Hat’s Quay security update, inspect approved service keys for unexpected keys with no expiration (CVE-2026-123710), and check database audit logs for namespaces containing _ or % that queried robot accounts (CVE-2026-110697).
  2. Upgrade OWASP CRS to 3.3.10, 4.25.1, or 4.28.0: Verify that rules/REQUEST-921-*.conf through REQUEST-943-*.conf include XML://@* alongside XML:/*.
  3. Upgrade soapbar to >= 0.13.0 (and pass trusted_certs or ca_certs to verify_envelope_bsp()), Apache Roller to >= 6.1.7, Apache Batik to >= 1.20, Apache FOP to >= 2.12, Kendo UI to >= 2026.4.1111, repmgr to >= 5.5.1, pappl-retrofit to >= 1.0b3, and Janus WebRTC to >= 1.4.2. Never pass untrusted .pt, .ckpt, .npz, or .yaml files into fairchem-core, fairseq, or fairseq2.

Timeline

  • 2026-03-04 to 2026-03-26: Trend Micro ZDI reports 30 RCE vulnerabilities in Meta FAIRChem, fairseq, and fairseq2 (ZDI-CAN-29081 through ZDI-CAN-29596).
  • 2026-10-23: ZDI notifies Meta of its intent to publish ZDI-26-924 through ZDI-26-953 as 0-day advisories after fairseq is archived and FAIRChem checkpoint deserialization reports remain unfixed.
  • 2026-11-11 (06:00 to 18:19 UTC): ZDI publishes ZDI-26-924 through ZDI-26-953; oss-security and NVD publish the Apache Roller 6.1.7 (15 CVEs), Apache Batik 1.20 / FOP 2.12 (8 CVEs), GNU Emacs 31.1 .dir-locals.el (debbugs#82213), glibc (CVE-2026-115819, CVE-2026-100290), pappl-retrofit (CVE-2026-123747), Red Hat Quay (CVE-2026-123710, CVE-2026-110697), Grafana (CVE-2026-111024, 111000, 102589, 107509), soapbar 0.13.0 (CVE-2026-64855), aeon 1.5.0 (CVE-2026-65820), Progress Kendo UI / Telerik (CVE-2026-124686..124694, CVE-2026-106152, 106156, 106137), repmgr 5.5.1 (CVE-2026-122043), Janus WebRTC 1.4.2 (CVE-2026-117373), and OWASP CRS 3.3.10 / 4.25.1 / 4.28.0 (CVE-2026-61619, CVE-2026-62971) advisories.

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References