{"id":"CVE-2026-118773","aliases":["CLSA-2026-1793790276","CLSA-2026-1794048371","CLSA-2026-1794048468","CLSA-2026-1794065402","DEBIAN-CVE-2026-118773","EUVD-2026-113329","GHSA-3g3m-2fjr-6pw4","UBUNTU-CVE-2026-118773"],"status":"published","title":"Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","severity":{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.0035,"percentile":0.29113,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400"],"published":"2026-10-29T18:27:47Z","modified":"2026-11-07T19:00:37Z","fixes":[{"ecosystem":"npm","package":"glob","fixed_in":["14.0.2"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"glob","fixed_in":["10.5.0-tuxcare.1","10.3.10-tuxcare.2","10.2.6-tuxcare.2"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"last_affected":"14.0.1"},{"fixed":"14.0.2"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.5.0-tuxcare.0"},{"fixed":"10.5.0-tuxcare.1"}]}],"versions":["10.5.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.3.10-tuxcare.0"},{"fixed":"10.3.10-tuxcare.2"}]}],"versions":["10.3.10","10.3.10-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.2.6-tuxcare.0"},{"fixed":"10.2.6-tuxcare.2"}]}],"versions":["10.2.6","10.2.6-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.3.3-tuxcare.0"},{"fixed":"10.3.3-tuxcare.1"}]}],"versions":["10.3.3"],"bundled":2},{"source":"osv","ecosystem":"Debian:12","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.2.7+~cs0.4.15-1","10.3.6+~cs0.4.15-1","10.3.6+~cs0.4.15-2","10.3.6+~cs0.4.15-3","10.3.6+~cs0.4.15-4","10.3.6+~cs0.4.15-5","10.3.6+~cs0.4.15-6","10.3.6+~cs0.4.15-7","10.3.6+~cs0.4.15-8","10.3.6+~cs0.4.15-9","13.0.6+~cs0.4.15-1","13.0.6+~cs0.4.15-2","8.0.3+~cs8.4.15-1","8.0.3+~cs8.4.15-2","8.0.3+~cs8.4.15-3","8.0.3+~cs8.4.15-4","8.1.0+~cs8.5.15-1"]},{"source":"osv","ecosystem":"Debian:13","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.2.7+~cs0.4.15-1","10.3.6+~cs0.4.15-1","10.3.6+~cs0.4.15-2","10.3.6+~cs0.4.15-3","10.3.6+~cs0.4.15-4","10.3.6+~cs0.4.15-5","10.3.6+~cs0.4.15-6","10.3.6+~cs0.4.15-7","10.3.6+~cs0.4.15-8","10.3.6+~cs0.4.15-9","13.0.6+~cs0.4.15-1","13.0.6+~cs0.4.15-2","8.1.0+~cs8.5.15-1"]},{"source":"osv","ecosystem":"Debian:14","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.2.7+~cs0.4.15-1","10.3.6+~cs0.4.15-1","10.3.6+~cs0.4.15-2","10.3.6+~cs0.4.15-3","10.3.6+~cs0.4.15-4","10.3.6+~cs0.4.15-5","10.3.6+~cs0.4.15-6","10.3.6+~cs0.4.15-7","10.3.6+~cs0.4.15-8","10.3.6+~cs0.4.15-9","13.0.6+~cs0.4.15-1","13.0.6+~cs0.4.15-2","8.1.0+~cs8.5.15-1"]},{"source":"osv","ecosystem":"npm","package":"glob","ranges":[{"type":"SEMVER","events":[{"introduced":"9.0.0"},{"fixed":"14.0.2"}]}]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.2.1-2","3.2.6-1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.0.5-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.1.2-4"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.1.3-2","7.1.6-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.1.6+~7.1.3-1","7.1.7+~cs7.5.19-2","7.2.1+~cs7.6.15-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.0.3+~cs8.4.15-1","8.0.3+~cs8.4.15-4build2","8.1.0+~cs8.5.15-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.3.6+~cs0.4.15-8build1","13.0.6+~cs0.4.15-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"node-glob","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.1.0+~cs8.5.15-1","10.3.6+~cs0.4.15-8build1"]}],"products":[{"vendor":"isaacs","product":"node-glob"}],"references":[{"url":"https://github.com/isaacs/node-glob/security/advisories/GHSA-3g3m-2fjr-6pw4","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/isaacs/node-glob/commit/4682e8c9babee1b385202ede36389634e12076d7","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/isaacs/node-glob/releases/tag/v14.0.2","tags":["x_refsource_MISC","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118773","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-3g3m-2fjr-6pw4"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/118xxx/CVE-2026-118773.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-118773","tags":["advisory"]},{"url":"https://github.com/isaacs/node-glob","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-118773","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-118773","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-118773","title":"Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T18:27:47.48Z","modified":"2026-10-30T17:12:23.906Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T14:20:03.827373Z"}],"euvd":[{"id":"EUVD-2026-113329","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T18:27:47Z","modified":"2026-10-30T17:12:23Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-02T16:59:05.567782Z"}],"ghsa":[{"id":"GHSA-3g3m-2fjr-6pw4","title":"Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal","description":"### Summary\n\nIn glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background.\n\nThe root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been rejected.\n\n### Details\n\nThis was reproduced on glob v13.0.6 (commit e80cb38ae60d6cbff9e75f39032a994858994d35).\n\nThe README documents that the signal option cancels the glob walk. However, in src/walker.ts, the following methods call cb() when this.signal?.aborted is true but do not return:\n\n- GlobUtil.walkCB()\n- GlobUtil.walkCB2()\n- GlobUtil.walkCBSync()\n- GlobUtil.walkCB2Sync()\n\nExample vulnerable pattern:\n\nif (this.signal?.aborted) cb()\n\nBecause execution continues after cb(), the walker still reaches processor.processPatterns(), readdirCB(), and recursive walkCB2() calls.\n\nThe issue was directly demonstrated against v13.0.6. A source-history review shows the same missing-return pattern is present in tagged releases from v9.0.0 through v13.0.6.\n\nThe issue affects both glob() and globStream().\n\nRecommended fix:\nChange each abort branch to return immediately:\n\nif (this.signal?.aborted) return cb()\n\n### Proof of concept\n\nEnvironment:\n- Linux x86_64\n- Node.js v22.23.3\n- npm 10.9.9\n- glob 13.0.6\n\nReproduction steps:\n\n1. Install the affected package:\n   npm init -y\n   npm install glob@13.0.6\n\n2. Run the attached PoC:\n   node poc/abort-continues-work.mjs\n\nThe PoC aborts after the first readdir() call, waits briefly, and counts how many more directory reads happen after the promise has already rejected.\n\nObserved output on the vulnerable version:\n\n{\n  \"rejection\": \"Error: probe-abort\",\n  \"readdirCalls\": 1365,\n  \"readdirCallsAtReject\": 5,\n  \"readdirCallsAfterReject\": 1360\n}\n\nExpected behavior:\nreaddirCallsAfterReject should be 0.\n\nA second PoC using AbortSignal.timeout() also reproduces the issue:\n\n{\n  \"rejection\": \"TimeoutError: The operation was aborted due to timeout\",\n  \"readdirCalls\": 133,\n  \"readdirCallsAtReject\": 1,\n  \"readdirCallsAfterReject\": 132\n}\n\nThe same test against a patched build with return cb() in the four abort branches stops immediately:\n\n{\n  \"readdirCalls\": 1,\n  \"readdirCallsAtReject\": 1,\n  \"readdirCallsAfterReject\": 0\n}\n\n### Impact\n\nThis is an availability issue.\n\nApplications that expose globbing over attacker-influenced patterns or attacker-controlled directory trees and use AbortSignal / AbortSignal.timeout() as a traversal budget can still perform significant filesystem I/O and CPU work after a request has already timed out or been canceled.\n\nRepeated timed-out requests can stack background glob walks and degrade worker throughput or service availability.\n\nNo confidentiality or integrity impact was observed.","status":"published","published":"2026-10-30T23:09:11Z","modified":"2026-10-30T23:09:15Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T14:41:42.013329Z"}],"nvd":[{"id":"CVE-2026-118773","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T19:17:19.72Z","modified":"2026-10-30T19:37:07.073Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T14:13:04.940026Z"}],"osv":[{"id":"CVE-2026-118773","title":"Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T18:27:47.48Z","modified":"2026-11-04T02:47:27.479968471Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-400"],"updated_at":"2026-11-04T02:53:45.692342Z"},{"id":"DEBIAN-CVE-2026-118773","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T19:17:19.72Z","modified":"2026-10-31T09:47:29.122092865Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:45:51.374409Z"},{"id":"GHSA-3g3m-2fjr-6pw4","title":"Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal","description":"### Summary\n\nIn glob 13.0.6, an aborted async walk rejects or emits an error but continues recursively reading directories in the background.\n\nThe root cause is that abort branches in src/walker.ts call cb() without returning. As a result, callers that rely on signal or AbortSignal.timeout() to bound glob traversal cost can still incur filesystem I/O and CPU work after the request has already been rejected.\n\n### Details\n\nThis was reproduced on glob v13.0.6 (commit e80cb38ae60d6cbff9e75f39032a994858994d35).\n\nThe README documents that the signal option cancels the glob walk. However, in src/walker.ts, the following methods call cb() when this.signal?.aborted is true but do not return:\n\n- GlobUtil.walkCB()\n- GlobUtil.walkCB2()\n- GlobUtil.walkCBSync()\n- GlobUtil.walkCB2Sync()\n\nExample vulnerable pattern:\n\nif (this.signal?.aborted) cb()\n\nBecause execution continues after cb(), the walker still reaches processor.processPatterns(), readdirCB(), and recursive walkCB2() calls.\n\nThe issue was directly demonstrated against v13.0.6. A source-history review shows the same missing-return pattern is present in tagged releases from v9.0.0 through v13.0.6.\n\nThe issue affects both glob() and globStream().\n\nRecommended fix:\nChange each abort branch to return immediately:\n\nif (this.signal?.aborted) return cb()\n\n### Proof of concept\n\nEnvironment:\n- Linux x86_64\n- Node.js v22.23.3\n- npm 10.9.9\n- glob 13.0.6\n\nReproduction steps:\n\n1. Install the affected package:\n   npm init -y\n   npm install glob@13.0.6\n\n2. Run the attached PoC:\n   node poc/abort-continues-work.mjs\n\nThe PoC aborts after the first readdir() call, waits briefly, and counts how many more directory reads happen after the promise has already rejected.\n\nObserved output on the vulnerable version:\n\n{\n  \"rejection\": \"Error: probe-abort\",\n  \"readdirCalls\": 1365,\n  \"readdirCallsAtReject\": 5,\n  \"readdirCallsAfterReject\": 1360\n}\n\nExpected behavior:\nreaddirCallsAfterReject should be 0.\n\nA second PoC using AbortSignal.timeout() also reproduces the issue:\n\n{\n  \"rejection\": \"TimeoutError: The operation was aborted due to timeout\",\n  \"readdirCalls\": 133,\n  \"readdirCallsAtReject\": 1,\n  \"readdirCallsAfterReject\": 132\n}\n\nThe same test against a patched build with return cb() in the four abort branches stops immediately:\n\n{\n  \"readdirCalls\": 1,\n  \"readdirCallsAtReject\": 1,\n  \"readdirCallsAfterReject\": 0\n}\n\n### Impact\n\nThis is an availability issue.\n\nApplications that expose globbing over attacker-influenced patterns or attacker-controlled directory trees and use AbortSignal / AbortSignal.timeout() as a traversal budget can still perform significant filesystem I/O and CPU work after a request has already timed out or been canceled.\n\nRepeated timed-out requests can stack background glob walks and degrade worker throughput or service availability.\n\nNo confidentiality or integrity impact was observed.","status":"published","published":"2026-10-30T23:09:11Z","modified":"2026-10-30T23:15:04.503965732Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T15:46:35.747385Z"},{"id":"UBUNTU-CVE-2026-118773","description":"Glob matches files using patterns the shell uses. From 9.0.0 until 14.0.2, abort branches in src/walker.ts, including GlobUtil.walkCB(), GlobUtil.walkCB2(), GlobUtil.walkCBSync(), and GlobUtil.walkCB2Sync(), invoke the callbacks without returning. After AbortSignal or AbortSignal.timeout() rejects or emits an error, execution can continue into processor.processPatterns(), readdirCB(), and recursive traversal. The issue affects glob() and globStream() when applications expose attacker-influenced patterns or directory trees and rely on cancellation as a traversal budget. Repeated timed-out requests can stack background filesystem operations and CPU work, degrading worker throughput or service availability; no confidentiality or integrity impact was observed. This issue is fixed in 14.0.2.","status":"published","published":"2026-10-29T19:17:00Z","modified":"2026-11-05T04:42:51Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-05T13:33:25.727744Z"},{"id":"CLSA-2026-1793790276","title":"TuxCare security update for glob (1 CVE)","description":"TuxCare rebuilt glob to address 1 CVE. Fixed in 10.5.0-tuxcare.1.","status":"published","published":"2026-11-04T12:04:36Z","modified":"2026-11-04T14:45:06.150156417Z","updated_at":"2026-11-04T15:03:54.132276Z"},{"id":"CLSA-2026-1794048371","title":"TuxCare security update for glob (1 CVE)","description":"TuxCare rebuilt glob to address 1 CVE. Fixed in 10.3.10-tuxcare.2.","status":"published","published":"2026-11-07T11:46:12Z","modified":"2026-11-07T13:15:02.331338863Z","updated_at":"2026-11-07T13:47:00.167603Z"},{"id":"CLSA-2026-1794048468","title":"TuxCare security update for glob (1 CVE)","description":"TuxCare rebuilt glob to address 1 CVE. Fixed in 10.2.6-tuxcare.2.","status":"published","published":"2026-11-07T11:47:49Z","modified":"2026-11-07T13:15:02.327946461Z","updated_at":"2026-11-07T13:47:00.167603Z"},{"id":"CLSA-2026-1794065402","title":"TuxCare security update for glob (2 CVEs)","description":"TuxCare rebuilt glob to address 2 CVEs. Fixed in 10.3.3-tuxcare.1.","status":"published","published":"2026-11-07T16:30:03Z","modified":"2026-11-07T19:00:37.800916685Z","updated_at":"2026-11-07T19:21:34.633914Z"}]}}