{"id":"CVE-2026-84890","aliases":["CLSA-2026-1790719646","CLSA-2026-1790756064","CLSA-2026-1792478858","CLSA-2026-1792867308","CLSA-2026-1794310630","DEBIAN-CVE-2026-84890","EUVD-2026-71634","GHSA-3xpg-4rpp-hhhm","GHSA-jr45-8vmc-qm54","GHSA-vmh5-mc38-953g","RHSA-2026:54389","RHSA-2026:54438","RHSA-2026:66008","UBUNTU-CVE-2026-84890","openSUSE-SU-2026:22111-1"],"status":"published","title":"undici vulnerable to Denial of Service via unbounded decompression of compressed responses","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00412,"percentile":0.3594,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2026-08-13T10:17:44Z","modified":"2026-11-10T13:15:07Z","fixes":[{"ecosystem":"npm","package":"undici","fixed_in":["7.29.1","8.10.2"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"node-undici","fixed_in":["8.10.2+dfsg+~cs3.2.2-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.15.0"},{"fixed":"7.29.1"}]}]},{"source":"ghsa","ecosystem":"npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.10.2"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.29.0-tuxcare.0"},{"fixed":"7.29.0-tuxcare.2"}]}],"versions":["7.29.0","7.29.0-tuxcare.1"],"bundled":7},{"source":"osv","ecosystem":"TuxCare:npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.28.0-tuxcare.0"},{"fixed":"7.28.0-tuxcare.3"}]}],"versions":["7.28.0","7.28.0-tuxcare.1","7.28.0-tuxcare.2"],"bundled":6},{"source":"osv","ecosystem":"TuxCare:npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.24.4-tuxcare.0"},{"fixed":"7.24.4-tuxcare.2"}]}],"versions":["7.24.4","7.24.4-tuxcare.1"],"bundled":13},{"source":"osv","ecosystem":"TuxCare:npm","package":"undici-types","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.29.0-tuxcare.0"},{"fixed":"7.29.0-tuxcare.2"}]}],"versions":["7.29.0","7.29.0-tuxcare.1"],"bundled":7},{"source":"osv","ecosystem":"TuxCare:npm","package":"undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.24.8-tuxcare.0"},{"fixed":"7.24.8-tuxcare.1"}]}],"versions":["7.24.8"],"bundled":14},{"source":"osv","ecosystem":"Debian:12","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0+dfsg1+~cs20.10.9.3-1","5.15.0+dfsg1+~cs20.10.9.3-1+deb12u1","5.15.0+dfsg1+~cs20.10.9.3-1+deb12u2","5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3","5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4","5.19.1+dfsg1+~cs20.10.9.5-1","5.19.1+dfsg1+~cs20.10.9.5-2","5.22.1+dfsg1+~cs20.10.10.2-1","5.26.3+dfsg1+~cs23.10.12-1","5.26.3+dfsg1+~cs23.10.12-2","5.26.3+dfsg1+~cs23.10.12-3","5.28.0+dfsg1+~cs23.11.12.3-1","5.28.0+dfsg1+~cs23.11.12.3-2","5.28.2+dfsg1+~cs23.11.12.3-1","5.28.2+dfsg1+~cs23.11.12.3-2","5.28.2+dfsg1+~cs23.11.12.3-3","5.28.2+dfsg1+~cs23.11.12.3-4","5.28.2+dfsg1+~cs23.11.12.3-5","5.28.2+dfsg1+~cs23.11.12.3-6","5.28.4+dfsg1+~cs23.12.11-1","5.28.4+dfsg1+~cs23.12.11-2","7.1.0+dfsg1+~cs24.12.10-1","7.15.0+dfsg+~cs3.2.0-1","7.15.0+dfsg+~cs3.2.0-3","7.16.0+dfsg+~cs3.2.0-1","7.16.0+dfsg+~cs3.2.0-2","7.18.2+dfsg+~cs3.2.0-1","7.2.3+dfsg1+~cs24.12.11-1","7.2.3+dfsg1+~cs24.12.11-2","7.24.5+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-2","7.24.6+dfsg+~cs3.2.0-3","7.3.0+dfsg1+~cs24.12.11-1","7.3.0+dfsg1+~cs24.12.11-2","8.10.2+dfsg+~cs3.2.2-1","8.5.0+dfsg+~cs3.2.0-1","8.5.0+dfsg+~cs3.2.0-2","8.5.0+dfsg+~cs3.2.0-3","8.9.0+dfsg+~cs3.2.0-1"]},{"source":"osv","ecosystem":"Debian:13","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.15.0+dfsg+~cs3.2.0-1","7.15.0+dfsg+~cs3.2.0-3","7.16.0+dfsg+~cs3.2.0-1","7.16.0+dfsg+~cs3.2.0-2","7.18.2+dfsg+~cs3.2.0-1","7.24.5+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-2","7.24.6+dfsg+~cs3.2.0-3","7.3.0+dfsg1+~cs24.12.11-1","7.3.0+dfsg1+~cs24.12.11-2","8.10.2+dfsg+~cs3.2.2-1","8.5.0+dfsg+~cs3.2.0-1","8.5.0+dfsg+~cs3.2.0-2","8.5.0+dfsg+~cs3.2.0-3","8.9.0+dfsg+~cs3.2.0-1"]},{"source":"osv","ecosystem":"Debian:14","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.10.2+dfsg+~cs3.2.2-1"}]}],"versions":["7.15.0+dfsg+~cs3.2.0-1","7.15.0+dfsg+~cs3.2.0-3","7.16.0+dfsg+~cs3.2.0-1","7.16.0+dfsg+~cs3.2.0-2","7.18.2+dfsg+~cs3.2.0-1","7.24.5+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-1","7.24.6+dfsg+~cs3.2.0-2","7.24.6+dfsg+~cs3.2.0-3","7.3.0+dfsg1+~cs24.12.11-1","7.3.0+dfsg1+~cs24.12.11-2","8.5.0+dfsg+~cs3.2.0-1","8.5.0+dfsg+~cs3.2.0-2","8.5.0+dfsg+~cs3.2.0-3","8.9.0+dfsg+~cs3.2.0-1"]},{"source":"osv","ecosystem":"npm","package":"undici","ranges":[{"type":"SEMVER","events":[{"introduced":"7.15.0"},{"fixed":"7.29.1"}]}]},{"source":"osv","ecosystem":"npm","package":"undici","ranges":[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.10.2"}]}]},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-bin","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-full-i18n","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-npm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:11.19.0-1.26.7.0.1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs26-npm-bin","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:26.7.0-1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"v8-14.6-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:14.6.202.34-1.26.7.0.1.5.2.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-bin","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-full-i18n","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-npm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:11.16.0-1.24.18.1.0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"nodejs24-npm-bin","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:24.18.1-0.2.2.hum1"}]}],"bundled":9},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"grafana12.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:12.4.10-0.2.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.22.1+dfsg1+~cs20.10.10.2-1ubuntu1","5.26.3+dfsg1+~cs23.10.12-2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.18.2+dfsg+~cs3.2.0-1build1","7.24.6+dfsg+~cs3.2.0-3","8.5.0+dfsg+~cs3.2.0-2","8.5.0+dfsg+~cs3.2.0-3","8.9.0+dfsg+~cs3.2.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"node-undici","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.3.0+dfsg1+~cs24.12.11-2","7.16.0+dfsg+~cs3.2.0-2","7.18.2+dfsg+~cs3.2.0-1","7.18.2+dfsg+~cs3.2.0-1build1"]},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"pi-coding-agent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.4-bp160.1.1"}]}],"bundled":11}],"products":[{"vendor":"nodejs","product":"undici"},{"vendor":"undici","product":"undici"}],"references":[{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-3xpg-4rpp-hhhm","tags":["Mitigation","Vendor Advisory","advisory","web","article","report"]},{"url":"https://cna.openjsf.org/security-advisories.html","tags":["Vendor Advisory","advisory","web","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84890","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/commit/2c7d7e1227043c644c4c32cfd1e276f4fd4fcb11","tags":["web"]},{"url":"https://github.com/nodejs/undici/commit/7aac7f12f757844763c8b8f1ab6e305e80d55838","tags":["web"]},{"url":"https://github.com/nodejs/undici/releases/tag/v7.29.1","tags":["web"]},{"url":"https://github.com/nodejs/undici/releases/tag/v8.10.2","tags":["web"]},{"url":"https://github.com/advisories/GHSA-3xpg-4rpp-hhhm"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/84xxx/CVE-2026-84890.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-84890","tags":["advisory"]},{"url":"https://github.com/nodejs/undici","tags":["package"]},{"url":"https://access.redhat.com/errata/RHSA-2026:54389","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-14257","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-69152","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-84947","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-85152","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-84933","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-18149","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-84890","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-85014","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-85008","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-48932","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54389.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2506433","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-14257","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14257","tags":["advisory"]},{"url":"https://github.com/juliangruber/brace-expansion","tags":["article"]},{"url":"https://github.com/juliangruber/brace-expansion/commit/a1bd33999ea75262c4749fff3bbb0d1372bd07b5","tags":["article"]},{"url":"https://www.npmjs.com/package/brace-expansion","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528802","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-18149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18149","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-pmjh-fq2x-6v4x","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2526627","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-48932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48932","tags":["advisory"]},{"url":"https://hackerone.com/reports/3564941","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2510722","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-69152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69152","tags":["advisory"]},{"url":"https://github.com/juliangruber/brace-expansion/commit/139d015104e71433ad52a41d19467c48ecbb2c7d","tags":["article"]},{"url":"https://github.com/juliangruber/brace-expansion/commit/1e30c930238d7162802d88a94189182def178dac","tags":["article"]},{"url":"https://github.com/juliangruber/brace-expansion/commit/688a99eeaab02627c2b89ba8ba4821fecfa659cf","tags":["article"]},{"url":"https://github.com/juliangruber/brace-expansion/commit/cb4b9e47cc2ec777c14b2b4492fb431a56f6a031","tags":["article"]},{"url":"https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-rgw5-rvv9-x895","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528772","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-84890","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-84933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84933","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-2jfj-6hjv-fm6j","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-84947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84947","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-2gqq-gqf2-x968","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528747","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-85008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85008","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-8436-99hf-9mmv","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528712","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-85014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85014","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-rx4f-c7p8-82vq","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528717","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-85152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-85152","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-vp8m-p9jh-q5pm","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2026:54438","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-84961","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54438.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528735","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-84961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84961","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-w293-vg96-wgc3","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2026:66008","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19534","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-18540","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-14199","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-28378","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19197","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_66008.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2521850","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-14199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14199","tags":["advisory"]},{"url":"https://grafana.com/security/security-advisories/cve-2026-14199/","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-18540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18540","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-r53p-7pc4-xj5r","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2524303","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19197","tags":["advisory"]},{"url":"https://grafana.com/security/security-advisories/cve-2026-19197","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2528759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19534","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19534","tags":["advisory"]},{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-rfgv-xxqx-mfg5","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2497887","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-28378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-28378","tags":["advisory"]},{"url":"https://grafana.com/security/security-advisories/cve-2026-28378","tags":["article"]},{"url":"https://ubuntu.com/security/CVE-2026-84890","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1279832","tags":["report"]},{"url":"https://bugzilla.suse.com/1283188","tags":["report"]},{"url":"https://bugzilla.suse.com/1283392","tags":["report"]},{"url":"https://bugzilla.suse.com/1283412","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-102276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-102277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-102278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-85008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-85014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-85024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-85152","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-84890","title":"undici vulnerable to Denial of Service via unbounded decompression of compressed responses","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T17:04:28.261Z","modified":"2026-09-04T18:33:28.246Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:20:08.391556Z"}],"euvd":[{"id":"EUVD-2026-71634","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T17:04:28Z","modified":"2026-09-04T18:33:28Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T18:01:11.774269Z"}],"ghsa":[{"id":"GHSA-3xpg-4rpp-hhhm","title":"undici vulnerable to Denial of Service via unbounded decompression of compressed responses","description":"### Impact\n\nThe `interceptors.decompress()` interceptor decompresses HTTP response bodies according to the untrusted `Content-Encoding` header. The number of decompression layers is capped at 5, but the total decompressed output size is not bounded and there is no option to limit it. A malicious or faulty upstream can return a small compressed payload (a compression bomb) that expands to hundreds of megabytes or gigabytes in client memory, exhausting memory and causing the Node.js process to crash or become unresponsive. Any application using the decompress interceptor to read responses from untrusted or compromised upstreams is affected.\n\n### Patches\n\nUpgrade to `7.29.1` or `8.10.2`. The interceptor now accepts a `maxSize` option (default 64 MiB) and rejects responses whose decompressed output exceeds it with a `ResponseExceededMaxSizeError`.\n\n### Workarounds\n\nOnce upgraded, set a conservative `maxSize` on the interceptor. Before upgrading, avoid using `interceptors.decompress()` with untrusted upstreams, or apply a custom interceptor that enforces a decompressed output size limit.","status":"published","published":"2026-09-29T18:20:37Z","modified":"2026-09-29T18:20:38Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:41:22.654187Z"}],"nvd":[{"id":"CVE-2026-84890","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T18:18:01.633Z","modified":"2026-09-11T16:55:29.047Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:12:44.082631Z"}],"osv":[{"id":"CVE-2026-84890","title":"undici vulnerable to Denial of Service via unbounded decompression of compressed responses","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T17:04:28.261Z","modified":"2026-10-28T02:31:01.72726849Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:45:18.482949Z"},{"id":"DEBIAN-CVE-2026-84890","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T18:18:01.633Z","modified":"2026-10-01T03:03:43.152137566Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:46:05.022702Z"},{"id":"GHSA-3xpg-4rpp-hhhm","title":"undici vulnerable to Denial of Service via unbounded decompression of compressed responses","description":"### Impact\n\nThe `interceptors.decompress()` interceptor decompresses HTTP response bodies according to the untrusted `Content-Encoding` header. The number of decompression layers is capped at 5, but the total decompressed output size is not bounded and there is no option to limit it. A malicious or faulty upstream can return a small compressed payload (a compression bomb) that expands to hundreds of megabytes or gigabytes in client memory, exhausting memory and causing the Node.js process to crash or become unresponsive. Any application using the decompress interceptor to read responses from untrusted or compromised upstreams is affected.\n\n### Patches\n\nUpgrade to `7.29.1` or `8.10.2`. The interceptor now accepts a `maxSize` option (default 64 MiB) and rejects responses whose decompressed output exceeds it with a `ResponseExceededMaxSizeError`.\n\n### Workarounds\n\nOnce upgraded, set a conservative `maxSize` on the interceptor. Before upgrading, avoid using `interceptors.decompress()` with untrusted upstreams, or apply a custom interceptor that enforces a decompressed output size limit.","status":"published","published":"2026-09-29T18:20:37Z","modified":"2026-09-29T18:30:41.143057118Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:36.092962Z"},{"id":"RHSA-2026:54389","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update","status":"published","published":"2026-08-13T10:17:44Z","modified":"2026-10-20T10:43:37.18683072Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:21.457353Z"},{"id":"RHSA-2026:54438","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-05T10:15:36Z","modified":"2026-10-20T10:43:34.57503475Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:21.457353Z"},{"id":"RHSA-2026:66008","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-10T10:17:09Z","modified":"2026-10-20T10:43:33.340874063Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"UBUNTU-CVE-2026-84890","description":"undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.","status":"published","published":"2026-09-04T18:18:00Z","modified":"2026-10-17T13:01:12.9892672Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:57:24.828975Z"},{"id":"CLSA-2026-1790719646","title":"TuxCare security update for undici (7 CVEs)","description":"TuxCare rebuilt undici to address 7 CVEs. Fixed in 7.29.0-tuxcare.2.","status":"published","published":"2026-09-29T22:07:26Z","modified":"2026-10-25T01:30:03.52180706Z","updated_at":"2026-11-02T15:43:48.65893Z"},{"id":"CLSA-2026-1790756064","title":"TuxCare security update for undici (6 CVEs)","description":"TuxCare rebuilt undici to address 6 CVEs. Fixed in 7.28.0-tuxcare.3.","status":"published","published":"2026-09-30T08:14:24Z","modified":"2026-10-15T09:47:53.491974208Z","updated_at":"2026-11-02T15:43:48.65893Z"},{"id":"CLSA-2026-1792478858","title":"TuxCare security update for undici (15 CVEs)","description":"TuxCare rebuilt undici to address 15 CVEs. Fixed in 7.24.4-tuxcare.2.","status":"published","published":"2026-10-20T06:47:38Z","modified":"2026-11-05T13:28:26.36826201Z","updated_at":"2026-11-05T16:37:45.64821Z"},{"id":"CLSA-2026-1792867308","title":"TuxCare security update for undici-types (7 CVEs)","description":"TuxCare rebuilt undici-types to address 7 CVEs. Fixed in 7.29.0-tuxcare.2.","status":"published","published":"2026-10-24T18:41:47Z","modified":"2026-10-25T01:30:06.623556274Z","updated_at":"2026-11-02T15:43:54.981307Z"},{"id":"CLSA-2026-1794310630","title":"TuxCare security update for undici (14 CVEs)","description":"TuxCare rebuilt undici to address 14 CVEs. Fixed in 7.24.8-tuxcare.1.","status":"published","published":"2026-11-10T12:37:11Z","modified":"2026-11-10T13:15:07.241296257Z","updated_at":"2026-11-10T13:29:51.103746Z"},{"id":"openSUSE-SU-2026:22111-1","title":"Security update for pi-coding-agent","description":"This update for pi-coding-agent fixes the following issues:\n\nChanges in pi-coding-agent:\n\n- Update to version 1.0.4 (1.0.3 was superseded the same day and\n  never submitted):\n  * BREAKING: provider azure-openai-responses renamed to azure,\n    now also serving Azure Foundry Chat Completions\n    (azure/deepseek-v4-pro first). Rename the provider key in\n    auth.json (or run /login again), models.json and\n    settings.json (defaultProvider, enabledModels and\n    modelThinkingLevels); sessions on the old provider fall back\n    and lose prompt cache. AZURE_OPENAI_* env vars unchanged\n  * --tools and --exclude-tools take *-patterns and --no-mcp\n    disables MCP for one run; --tools keeps MCP tools unless an\n    entry starts with mcp__\n  * Codemode read() on image files yields an image block image()\n    shows, and image() also saves each image to a temp file for\n    later turns\n  * Fix fenced-code highlighting past the first line, MCP OAuth\n    native-client registration, MCP shutdown racing a connecting\n    server, Bedrock stalled-stream retries and frozen codemode\n    built-ins, plus ChatGPT-login, EIO-on-closed-terminal and\n    output-file-permission fixes\n  * Many more fixes and improvements; see upstream's release notes\n    for the full list\n- Refresh the vendored node_modules 1.0.2 -\u003e 1.0.4: the ten\n  @earendil-works packages move to 1.0.4; nanoid, postcss and\n  vite move too but are dev-only and not shipped. Still 119\n  shipped modules and the licence union is unchanged\n  * CVE-2026-102276 (boo#1283188): brace-expansion is 5.0.12, above\n    the 5.0.10 fix floor, so the package is not affected by it\n  * CVE-2026-102277 (boo#1283392) and CVE-2026-102278\n    (boo#1283412): brace-expansion is 5.0.12, at the 5.0.12 and\n    above the 5.0.11 fix floors, so the package is not affected\n    by them\n\n- Update to version 1.0.2: patch releases on the 1.0 API, with no\n  breaking changes\n  * models.json takes samplingParamsByThinkingLevel next to the\n    existing samplingParams, so an OpenAI-compatible model can set\n    temperature, top_p and the like separately for off, minimal, low,\n    medium, high, xhigh and max. Model defaults, the effective level's\n    override and the request are merged per key, modelOverrides merges\n    per level, and the levels are pi's own, not the provider's\n    thinkingLevelMap values. Only openai-completions, openai-responses\n    and azure-openai-responses apply them\n  * MCP servers can be enabled, disabled or re-scoped per project\n    from a .pi/mcp.json entry without a command or url, and /mcp\n    toggles a user-level server for the current project\n  * oauth.clientRegistration: \"cimd\" identifies pi by its Client ID\n    Metadata Document instead of dynamic client registration\n  * pi.registerToolRenderer() picks how calls to a tool that is not\n    registered yet are drawn, such as MCP tools in a resumed session\n  * Cloudflare's Clef and Clef Flash classifier models are usable\n    from codemode scripts and extensions\n  * A codemode script printing in a loop now fails at 16 Mi\n    characters or 100000 items instead of running pi out of memory\n  * MCP tool calls in resumed sessions and HTML exports no longer\n    render fully expanded until their server connects\n  * JPEG, GIF and WebP images that extensions draw through Image now\n    appear in Kitty, Ghostty, WezTerm and Warp, and fullscreen Kitty\n    images no longer collapse to a one-row strip after scrolling in\n    WezTerm\n  * Many more fixes and improvements; see upstream's release notes\n    for the full list\n- Refresh the vendored node_modules over 1.0.0 -\u003e 1.0.2: the ten\n  @earendil-works packages move to 1.0.2, with pi-telemetry the one\n  that was already at 1.0.2 in the 1.0.1 tree, plus\n  @anthropic-ai/sdk to 0.129.0. No module leaves or joins the 119\n  shipped ones and the licence union is unchanged\n  * CVE-2026-102276 (boo#1283188): brace-expansion is 5.0.12, above\n    the 5.0.10 fix floor, so the package is not affected by it.\n    Upstream's 1.0.1 made it a direct dependency, but this package\n    vendored 5.0.12 already at 1.0.0\n  * CVE-2026-102277 (boo#1283392) and CVE-2026-102278 (boo#1283412):\n    brace-expansion is 5.0.12, at the 5.0.12 and above the 5.0.11\n    fix floors, so the package is not affected by them\n- Fix the %prep comment on Source10: upstream ships no shrinkwrap\n  since 1.0.1\n\n- Update to version 1.0.0. This is a major release with breaking\n  behaviour changes, not a patch release:\n  * BREAKING: the interactive TUI runs fullscreen by default now,\n    so the terminal's normal scrollback is gone. Set tuiMode to\n    \"regular\" in the settings, or pass --tui-mode regular, for\n    the old behaviour\n  * BREAKING: MCP OAuth credentials are keyed by server name and\n    URL instead of by URL alone, so two servers behind one URL can\n    hold separate accounts. Credentials written by 0.99.x move to\n    the first server that reads them; other servers on the same\n    URL have to sign in again\n  * BREAKING: MCP sign-in enforces RFC 9207 and rejects an\n    authorization response whose iss names another authorization\n    server. A server advertising a wrong or missing one needs the\n    new oauth.authServerMetadataUrl setting\n  * BREAKING: --provider without --model fails now instead of\n    silently running another provider's default model\n  * BREAKING: codemode scripts have to probe for a tool with\n    \"name\" in tools; typeof tools.name no longer finds it, and\n    the codemode description carries one call line per tool\n    instead of the full declaration\n  * BREAKING: quietStartup also takes \"header\", which keeps the\n    version and key hints but hides the model scope line and the\n    loaded-resource listing\n  * Sign in with Radius from /login, which can set up the Radius\n    MCP server too, and with a copy code for Anthropic when the\n    browser runs on another machine\n  * Codemode scripts call models.generateImages() to run image\n    models with the session's credentials. Codemode needs about\n    40% fewer prompt tokens and its errors now name close matches\n    and the expected argument shape\n  * MCP step-up sign-in keeps the scopes it already had, so a\n    server asking for more no longer causes a sign-in loop\n  * Fix MCP tools that tool_search loaded being dropped on resume\n    and /reload, user messages keeping two full-width copies of\n    every rendered line, and slash command completion after\n    leading whitespace\n  * Fix the memory a long assistant message keeps in the\n    transcript (about a fifth of before), colour bleeding past\n    highlights in fullscreen mode, and the system theme\n    oversaturating pastel palettes\n  * Many more fixes and improvements; see upstream's release notes\n- Refresh the vendored node_modules: the ten @earendil-works\n  packages go 0.99.2 -\u003e 1.0.0 and nothing else in the 119 shipped\n  modules moves, so the license union is unchanged. pi-agent-core\n  drops its chord, pi-telemetry, diff, ignore and yaml deps, all\n  of which other packages in the tree still pull in.\n- The codemode sandbox is still WebAssembly only (quickjs.wasm\n  plus five .so-named WASI modules, no ELF), so the package stays\n  noarch\n\n- Update to version 0.99.2:\n  * MCP servers with the default codemode exposure no longer block\n    the first prompt; they are listed in a short mcp_servers\n    system prompt section and scripts find their tools with\n    searchTools() and describeNamespace()\n  * More MCP authentication: oauth.clientName for servers that\n    only accept known OAuth clients, and \"auth\": {\"provider\": ...}\n    to send a provider's /login token to an HTTP server\n  * Anthropic workload identity federation from\n    ANTHROPIC_FEDERATION_RULE_ID, ANTHROPIC_ORGANIZATION_ID and\n    ANTHROPIC_IDENTITY_TOKEN_FILE\n  * /reload enables tools newly added to the defaultTools setting\n  * Fix codemode image() accepting malformed base64 or\n    unsupported image types, which made every later provider\n    request fail with HTTP 400\n  * Fix codemode scripts calling the wrong MCP tool when two\n    names differ only in \"-\" and \"_\"; such names now\n    normalise to \"_\"\n  * Fix new sessions intermittently ignoring the saved default\n    model, or warning that no models are available, for\n    extension-registered providers with a stored credential\n  * Fix Anthropic requests failing when a tool schema uses\n    minimum or maximum, which strict tool use rejects; such\n    tools are sent non-strict\n  * Fix provider retries firing immediately on an unparseable\n    Retry-After date, and prompt submission slowing as a\n    session grows\n  * Many more fixes and improvements; see upstream's release notes\n- Refresh the vendored node_modules: the ten @earendil-works\n  packages go 0.99.1 -\u003e 0.99.2 and nothing else in the 119\n  shipped modules moves, so the license union is unchanged\n  * CVE-2026-102277 (boo#1283392): brace-expansion is 5.0.12,\n    at the fix floor, so the package is not affected by it\n  * CVE-2026-102278 (boo#1283412): brace-expansion is 5.0.12,\n    above the 5.0.11 fix floor, so the package is not\n    affected by it\n\n- Update to version 0.99.1 (upstream jumped from 0.87.1; no\n  0.88-0.98 releases exist):\n  * Codemode and MCP: model-written JavaScript runs in a QuickJS\n    WebAssembly sandbox calling pi's tools in parallel; MCP servers\n    over stdio/HTTP with OAuth come from mcp.json and are managed\n    with /mcp and pi mcp add|remove|list|login|logout\n  * New default system theme follows the terminal's own palette,\n    with #rgb/oklch()/okhsl() colors and light/dark rebuilding\n  * Sign in with ChatGPT on the OpenAI provider; inherited OpenAI\n    Codex provider renamed \"OpenAI Codex (legacy)\"\n  * Experimental virtual models route each request to a physical\n    model; llama.cpp models gain classifier support\n  * GPT-6.1 Sol joins OpenAI, Azure OpenAI and OpenAI Codex, and\n    becomes the default Codex model\n  * Built-in extensions and tools are named builtin:\u003cname\u003e,\n    --no-extensions disables them too; tool APIs gain exposure,\n    namespaces, annotations, structuredContent, ctx.executeTool()\n  * Sessions are created on the first user message, so pi no longer\n    loses them when it exits before the first response\n  * Many more fixes and improvements; see upstream's release notes\n- Refresh package-lock.json (now the full npm-generated lockfile,\n  integrity complete) and the vendored node_modules archive:\n  116 -\u003e 119 shipped modules, with @earendil-works/pi-codemode,\n  @earendil-works/pi-mcp and quickjs-wasi new, openai 6.40.0 -\u003e\n  7.19.0 and agent-base/https-proxy-agent 7.x -\u003e 9.x; license union\n  unchanged\n- The new codemode sandbox ships as WebAssembly only (quickjs.wasm\n  plus five .so-named WASI modules, no ELF), so the package stays\n  noarch\n\n- Update to version 0.87.1:\n  * New frontier models: Claude Opus 5.5, GPT-6 Sol and Luna\n    across providers; Grok 4.7 default for xAI\n  * Fix split-turn compaction summaries refused by Claude\n    Fable 5.1; invalid --mode values now error out\n  * Undici 8.10.2 retained: the 8 CVE batch fixed since\n    0.86.1 (CVE-2026-84961, CVE-2026-85024, CVE-2026-85008,\n    CVE-2026-84947, CVE-2026-85152, CVE-2026-84890,\n    CVE-2026-84933, CVE-2026-85014; boo#1279832)\n- Refresh the vendored node_modules\n","status":"published","published":"2026-10-09T15:27:19Z","modified":"2026-10-19T17:23:14.589993257Z","updated_at":"2026-11-02T16:58:42.426393Z"}]}}