📁 OpenClaw
September 6, 2026 · View on GitHub
Complete listing of all 157 security advisories tracked for OpenClaw. For the summary dashboard, see the main README.
Last updated: 2026-09-06 15:11 UTC
GHSAs with CVE IDs (59)
| GHSA | CVE | Severity | Title | Packages | Fixed in | Published |
|---|---|---|---|---|---|---|
| GHSA-j472-gf56-x589 | CVE-2026-53836 |  | OpenClaw: PowerShell encoded-command aliases could miss exec allowlist checks | npm/openclaw | 2026.5.12 | 2026-07-02 |
| GHSA-7hxm-f538-3xp6 | CVE-2026-53811 | | OpenClaw: Matrix allowFrom could bind to mutable display names | npm/openclaw | 2026.5.7 | 2026-07-02 |
| GHSA-3c6j-hq33-3jv4 | CVE-2026-53816 | | OpenClaw: Paired nodes could forge exec lifecycle events without system.run provenance | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-vxx3-6hc9-7cc3 | CVE-2026-53806 | | OpenClaw: Combined POSIX shell options could confuse exec revalidation | npm/openclaw | 2026.5.12 | 2026-07-02 |
| GHSA-rj6p-xmxr-qj4h | CVE-2026-53818 |  | OpenClaw: MCP loopback could skip owner-only tool policy for non-owner callers | npm/openclaw | 2026.4.24 | 2026-07-02 |
| GHSA-275c-xpvc-jgfw | CVE-2026-53830 | | OpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload | npm/openclaw | 2026.4.22 | 2026-07-02 |
| GHSA-p39j-x9h5-q66m | CVE-2026-53809 | | OpenClaw: Embedded runner policy could be confused by provider aliases | npm/openclaw | 2026.4.25 | 2026-07-02 |
| GHSA-v8cx-933x-r976 | CVE-2026-53813 | | OpenClaw: Fake package roots could influence memory-core artifact loading | npm/openclaw | 2026.4.25 | 2026-07-02 |
| GHSA-8wg3-5mcm-fjq8 | CVE-2026-53819 | | OpenClaw: Workspace .env could override Homebrew executable selection for skill install flows | npm/openclaw | 2026.5.27 | 2026-07-02 |
| GHSA-77pv-3w4q-vrj5 | CVE-2026-53834 | | OpenClaw: QQBot pre-dispatch slash commands could skip allowFrom checks | npm/openclaw | 2026.4.27 | 2026-07-02 |
| GHSA-gp79-m99v-gjmh | CVE-2026-53837 | | OpenClaw: Mattermost handlers could fall open when channel type was missing | npm/openclaw | 2026.5.6 | 2026-07-02 |
| GHSA-jvm4-4j77-39p6 | CVE-2026-53833 | | OpenClaw: QQBot streaming command could mutate config without explicit allowFrom | npm/openclaw | 2026.4.29 | 2026-07-02 |
| GHSA-83w9-h5wv-j9xm | CVE-2026-53838 | | OpenClaw: Node pairing reconnection could confuse approval scope state | npm/openclaw | 2026.5.27 | 2026-07-02 |
| GHSA-mhq8-78pj-5j79 | CVE-2026-53831 | | OpenClaw's POSIX node system.run safe-bin allowlist could be widened by shell expansion | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-mgq6-vr84-7m2j | CVE-2026-35630 | | OpenClaw: QQBot native approval buttons did not enforce configured approver identity | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-6fvr-66p3-3qj4 | CVE-2026-53814 | | OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority | npm/openclaw | 2026.5.20 | 2026-07-02 |
| GHSA-chr9-m4q2-76hw | CVE-2026-53817 | | OpenClaw: Control UI locality spoofing could mint a durable admin device token | npm/openclaw | 2026.5.22 | 2026-07-02 |
| GHSA-rggc-m335-3wvj | CVE-2026-53832 | | OpenClaw: Same-host trusted-proxy deployments could accept local forged identity headers | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-v6r2-jh58-xx6w | CVE-2026-53810 | | OpenClaw's marketplace runtime extension metadata could point at unscanned payloads | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-2hfg-4fh4-qp7f | CVE-2026-53812 | | OpenClaw's browser act interactions could bypass private-network navigation checks | npm/openclaw | 2026.5.18 | 2026-07-02 |
| GHSA-q7q8-3mgw-q67r | CVE-2026-53815 | | OpenClaw: Message read actions could skip channel allowlist checks | npm/openclaw | 2026.5.19 | 2026-07-02 |
| GHSA-4hpg-mp64-x7xq | CVE-2026-53854 | | OpenClaw: Internal/webchat command auth could inherit ownerAllowFrom wildcard state | npm/openclaw | 2026.4.25 | 2026-06-18 |
| GHSA-8mg9-j9cf-54cj | CVE-2026-53852 |  | OpenClaw: Empty-scope device re-pairing could confuse caller scope containment | npm/openclaw | 2026.4.25 | 2026-06-18 |
| GHSA-rx78-29qr-5hq8 | CVE-2026-53865 | | OpenClaw: Workspace-derived service PATH could influence trash command selection | npm/openclaw | 2026.5.2 | 2026-06-18 |
| GHSA-wc84-j36w-pw4x | CVE-2026-53858 | | OpenClaw: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots | npm/openclaw | 2026.5.2 | 2026-06-18 |
| GHSA-cw4q-gqg5-g38h | CVE-2026-53849 | | OpenClaw: Discord allowFrom could bind to mutable display names | npm/openclaw | 2026.5.7 | 2026-06-18 |
| GHSA-mpc8-jxjh-qpgh | CVE-2026-53850 | | OpenClaw: Focus command could miss controlScope enforcement | npm/openclaw | 2026.4.25 | 2026-06-18 |
| GHSA-24vr-rprv-67rf | CVE-2026-53846 | | OpenClaw: Workspace .env npm_execpath could influence bundled runtime dependency install | npm/openclaw | 2026.4.29 | 2026-06-18 |
| GHSA-v2ww-5rh7-2h5v | CVE-2026-53853 | | OpenClaw: Linux and macOS exec allowlists skipped configured argument patterns | npm/openclaw | 2026.5.12 | 2026-06-18 |
| GHSA-8j37-5w68-wj2g | CVE-2026-53860 | | OpenClaw: BlueBubbles sender policy could match mutable conversation identifiers | npm/openclaw | 2026.5.7 | 2026-06-18 |
| GHSA-72fw-cqh5-f324 | CVE-2026-53844 | | OpenClaw: memory-wiki shared search could miss session visibility checks | npm/openclaw | 2026.4.29 | 2026-06-18 |
| GHSA-rwp6-7w3q-75fq | CVE-2026-53856 | | OpenClaw: Config recovery could restore openclaw.json with broad file permissions | npm/openclaw | 2026.4.24 | 2026-06-18 |
| GHSA-8c59-hr4w-qg69 | CVE-2026-53857 | | OpenClaw: Zalo allowFrom could bind to mutable display names | npm/openclaw | 2026.5.3 | 2026-06-18 |
| GHSA-68xw-r643-9p5w | CVE-2026-53845 | | OpenClaw: Skill-command dispatch could skip before-tool-call hooks | npm/openclaw | 2026.5.6 | 2026-06-18 |
| GHSA-x629-46cc-7xgw | CVE-2026-53847 | | OpenClaw: Active Memory write scope could mutate global config | npm/openclaw | 2026.5.6 | 2026-06-18 |
| GHSA-w9hf-3pp7-pvxv | CVE-2026-53841 | | OpenClaw: Exported session HTML could keep unsafe markdown links | npm/openclaw | 2026.5.12 | 2026-06-18 |
| GHSA-fcvx-5cxc-v5p8 | CVE-2026-53851 | | OpenClaw: Slack reaction events could ignore reaction notification settings | npm/openclaw | 2026.5.12 | 2026-06-18 |
| GHSA-9v8j-9c9g-w66c | CVE-2026-53862 | | OpenClaw: Bootstrap token replay could widen pending pairing scopes | npm/openclaw | 2026.5.12 | 2026-06-18 |
| GHSA-5cj2-3jr2-5h77 | CVE-2026-53855 | | OpenClaw: Shell positional parameters could weaken strict inline-eval checks | npm/openclaw | 2026.4.2 | 2026-06-18 |
| GHSA-gxg4-2rrr-jhc7 | CVE-2026-53859 | | OpenClaw: Hostname checks could treat trailing-dot hosts inconsistently | npm/openclaw | 2026.5.26 | 2026-06-18 |
| GHSA-cwpp-5962-q4f6 | CVE-2026-53848 | | OpenClaw: Exec allowlist could miss side effects from transparent command wrappers | npm/openclaw | 2026.5.26 | 2026-06-18 |
| GHSA-c226-q6fx-6j6c | CVE-2026-53861 | | OpenClaw: macOS Swift exec allowlist missed combined POSIX inline flags | npm/openclaw | 2026.5.6 | 2026-06-18 |
| GHSA-985f-72mj-8gf7 | CVE-2026-53863 | | OpenClaw: Tool group policy callers could accept unvalidated group IDs | npm/openclaw | 2026.4.25 | 2026-06-18 |
| GHSA-fq9j-vw4w-fr6v | CVE-2026-53842 | | OpenClaw: Workspace .env CLOUDSDK_PYTHON could influence Gmail setup gcloud execution | npm/openclaw | 2026.5.2 | 2026-06-18 |
| GHSA-f397-5vjw-v2c2 | CVE-2026-53866 | | OpenClaw: Shell inline-command parsing could miss an allowlist check | npm/openclaw | 2026.5.12 | 2026-06-18 |
| GHSA-q99w-vh6v-q3v7 | CVE-2026-53843 | | OpenClaw: Pairing-scoped device session could restore revoked node token authority | npm/openclaw | 2026.5.26 | 2026-06-18 |
| GHSA-ccwh-wwpp-6wg5 | CVE-2026-53864 | | OpenClaw: Host environment sanitizer missed two Node.js control variables | npm/openclaw | 2026.5.26 | 2026-06-18 |
| GHSA-rjxq-qqhf-8hwh | CVE-2026-53840 | | OpenClaw: MCP Streamable HTTP redirects could forward configured custom headers to another origin | npm/openclaw | 2026.5.12 | 2026-06-17 |
| GHSA-mj5r-hh7j-4gxf | CVE-2026-28480 | | OpenClaw Telegram allowlist authorization accepted mutable usernames | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-rq6g-px6m-c248 | CVE-2026-28469 | | OpenClaw Google Chat shared-path webhook target ambiguity allowed cross-account policy-context misrouting | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-3fqr-4cg8-h96q | CVE-2026-26317 | | OpenClaw affected by cross-site request forgery (CSRF) through loopback browser mutation endpoints | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-q447-rj3r-2cgh | CVE-2026-28478 | | OpenClaw affected by denial of service via unbounded webhook request body buffering | npm/openclaw, npm/clawdbot | 2026.2.13 | 2026-02-18 |
| GHSA-h89v-j3x9-8wqj | CVE-2026-28452 | | OpenClaw affected by denial of service through unguarded archive extraction allowing high expansion/resource abuse (ZIP/TAR) | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-w2cg-vxx6-5xjg | CVE-2026-29612 | | OpenClaw: denial of service through large base64 media files allocating large buffers before limit checks | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-g34w-4xqq-h79m | CVE-2026-26328 | | OpenClaw iMessage group allowlist authorization inherited DM pairing-store identities | npm/openclaw, npm/clawdbot | 2026.2.14 | 2026-02-18 |
| GHSA-mr32-vwc2-5j6h | CVE-2026-28458 | | OpenClaw's Browser Relay /cdp websocket is missing auth which could allow cross-tab cookie access | npm/openclaw, npm/moltbot | 2026.2.1 | 2026-02-17 |
| GHSA-q284-4pvr-m585 | CVE-2026-25157 | | OpenClaw/Clawdbot has OS Command Injection via Project Root Path in sshNodeCommand | npm/clawdbot | 2026.1.29 | 2026-02-02 |
| GHSA-g8p2-7wf7-98mq | CVE-2026-25253 | | OpenClaw/Clawdbot has 1-Click RCE via Authentication Token Exfiltration From gatewayUrl | npm/clawdbot | 2026.1.29 | 2026-02-02 |
| GHSA-mc68-q9jw-2h3v | CVE-2026-24763 | | OpenClaw/Clawdbot Docker Execution has Authenticated Command Injection via PATH Environment Variable | npm/clawdbot | 2026.1.29 | 2026-02-02 |
GHSAs Without CVE — Potential Future CVEs (54)
| GHSA | Severity | Title | CWEs | Fixed in | Published |
|---|---|---|---|---|---|
| GHSA-w4v6-g3wm-w36c |  | OpenClaw: QQBot admin commands could skip DM-only and allowFrom policy | CWE-863 | 2026.4.29 | 2026-07-02 |
| GHSA-r2c6-8jc8-g32w | | Duplicate Advisory: 1-Click RCE via Authentication Token Exfiltration From gatewayUrl | CWE-669 | 2026.1.29 | 2026-02-02 |
| GHSA-ffhm-8fwq-7q27 | | Duplicate Advisory: OpenClaw: PowerShell encoded-command aliases could miss exec allowlist checks | CWE-184 | 2026.5.12 | 2026-06-13 |
| GHSA-35c7-4r45-9gv3 | | Duplicate Advisory: OpenClaw: QQBot pre-dispatch slash commands could skip allowFrom checks | CWE-863 | 2026.4.27 | 2026-06-13 |
| GHSA-3qg8-hq7j-jj33 | | Duplicate Advisory: OpenClaw: Same-host trusted-proxy deployments could accept local forged identity headers | CWE-290 | 2026.5.18 | 2026-06-13 |
| GHSA-2w22-3f6x-3hf4 | | Duplicate Advisory: Workspace-derived service PATH could influence trash command selection | CWE-426 | — | 2026-06-16 |
| GHSA-vr6h-vxqj-3pjx | | Duplicate Advisory: Host environment sanitizer missed two Node.js control variables | CWE-184 | — | 2026-06-16 |
| GHSA-v383-2wgg-v483 | | Duplicate Advisory: Shell inline-command parsing could miss an allowlist check | CWE-862 | — | 2026-06-16 |
| GHSA-3v3j-737j-7g74 | | Duplicate Advisory: Linux and macOS exec allowlists skipped configured argument patterns | CWE-693 | — | 2026-06-16 |
| GHSA-4qgr-57jq-93vh | | Duplicate Advisory: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots | CWE-426 | — | 2026-06-16 |
| GHSA-w7m7-3xcf-mp48 | | Duplicate Advisory: Zalo allowFrom could bind to mutable display names | CWE-290 | — | 2026-06-16 |
| GHSA-27pq-2ph8-8x25 | | Duplicate Advisory: Shell positional parameters could weaken strict inline-eval checks | CWE-184 | — | 2026-06-16 |
| GHSA-qp5j-jr73-m2pw | | Duplicate Advisory: Workspace .env npm_execpath could influence bundled runtime dependency install | CWE-426 | — | 2026-06-16 |
| GHSA-p44v-rx83-vjp4 | | Duplicate Advisory: Discord allowFrom could bind to mutable display names | CWE-290 | — | 2026-06-16 |
| GHSA-9fr2-p65v-gqxq | | Duplicate Advisory: Workspace .env CLOUDSDK_PYTHON could influence Gmail setup gcloud execution | CWE-426 | — | 2026-06-16 |
| GHSA-wrmq-9fc4-gwwj | | Duplicate Advisory: Pairing-scoped device session could restore revoked node token authority | CWE-613 | — | 2026-06-16 |
| GHSA-p73f-w79w-jqr5 | | OpenClaw: Native command authorization could skip owner-command enforcement | CWE-863 | 2026.5.6 | 2026-07-02 |
| GHSA-77q5-rr5v-x43q | | OpenClaw: Trusted retry endpoint checks could match hostname prefixes | CWE-20, CWE-345, CWE-1023 | 2026.5.7 | 2026-07-02 |
| GHSA-w5ww-7chg-mxcq | | OpenClaw: Telegram interactive callbacks could skip commands.allowFrom | CWE-863 | 2026.5.6 | 2026-07-02 |
| GHSA-xr4f-mjxj-w6w5 | | OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes | CWE-863 | 2026.5.4 | 2026-07-02 |
| GHSA-qjpc-qf9m-xwmr | | OpenClaw: Trusted-proxy Control UI WebSocket accepted client-declared scopes before pairing | CWE-862, CWE-863 | 2026.5.18 | 2026-07-02 |
| GHSA-c29c-2q9c-pc86 | | OpenClaw: Slack allowFrom could bind to mutable display names | CWE-290 | 2026.5.3 | 2026-07-02 |
| GHSA-hw9r-h9mr-4jff | | OpenClaw: Scoped chat.send route inheritance could bypass admin command scope gates | CWE-862, CWE-863 | 2026.5.18 | 2026-07-02 |
| GHSA-2j8v-hwgc-x698 | | OpenClaw: Shell wrapper argv could change between approval and execution | CWE-284 | 2026.5.18 | 2026-07-02 |
| GHSA-xww8-gqvh-92x9 | | OpenClaw: Exec approval display truncation could hide the command being approved | CWE-284, CWE-863 | 2026.5.18 | 2026-07-02 |
| GHSA-c85p-9pvr-f7f5 | | Duplicate Advisory: OpenClaw: Node pairing reconnection could confuse approval scope state | CWE-367 | 2026.5.27 | 2026-06-13 |
| GHSA-chqm-wxm2-w73w | | Duplicate Advisory: OpenClaw: Mattermost handlers could fall open when channel type was missing | CWE-636 | 2026.5.6 | 2026-06-13 |
| GHSA-8wmm-344f-mpjg | | Duplicate Advisory: Tool group policy callers could accept unvalidated group IDs | CWE-639 | — | 2026-06-16 |
| GHSA-g796-jqmx-wf9q | | Duplicate Advisory: macOS Swift exec allowlist missed combined POSIX inline flags | CWE-184 | — | 2026-06-16 |
| GHSA-vqx6-6j84-2794 | | Duplicate Advisory: Hostname checks could treat trailing-dot hosts inconsistently | CWE-918 | — | 2026-06-16 |
| GHSA-r2fx-hp6p-pgrm | | Duplicate Advisory: Internal/webchat command auth could inherit ownerAllowFrom wildcard state | CWE-863 | — | 2026-06-16 |
| GHSA-vqj9-vhg4-27mg | | Duplicate Advisory: Config recovery could restore openclaw.json with broad file permissions | CWE-732 | — | 2026-06-16 |
| GHSA-c8w7-9w9h-x69q | | Duplicate Advisory: Slack reaction events could ignore reaction notification settings | CWE-862 | — | 2026-06-16 |
| GHSA-gw2c-6hcg-5g52 | | Duplicate Advisory: Focus command could miss controlScope enforcement | CWE-862 | — | 2026-06-16 |
| GHSA-58wc-8wrv-xp9j | | Duplicate Advisory: Active Memory write scope could mutate global config | CWE-266 | — | 2026-06-16 |
| GHSA-x7cf-6gp3-q5f8 | | Duplicate Advisory: MCP Streamable HTTP redirects could forward configured custom headers to another origin | CWE-522 | — | 2026-06-16 |
| GHSA-6jm4-83g2-35gv | | Duplicate Advisory: memory-wiki shared search could miss session visibility checks | CWE-862 | — | 2026-06-16 |
| GHSA-9c3v-684m-579c | | OpenClaw MCP SSE redirects could forward Authorization headers | CWE-200, CWE-522, CWE-601 | 2026.6.5 | 2026-07-01 |
| GHSA-4m3v-q747-pc6h | | OpenClaw: Mattermost slash token revocation could lag until monitor refresh | CWE-613 | 2026.4.24 | 2026-07-02 |
| GHSA-6c4r-g249-wv3c | | OpenClaw: Sandboxed session spawn could expose the real workspace path to child prompts | CWE-668 | 2026.4.26 | 2026-07-02 |
| GHSA-hcm3-8f6r-6xwg | | OpenClaw: Browser debug/export routes could reuse already-open blocked tabs | CWE-862 | 2026.4.29 | 2026-07-02 |
| GHSA-grc3-2j34-p6gm | | OpenClaw: message.action forwarding could send Gateway credentials to model-supplied loopback URLs | CWE-522 | 2026.5.2 | 2026-07-02 |
| GHSA-cqwv-9qjx-vxw2 | | OpenClaw: Skill Workshop apply flow could override pending approval | CWE-807 | 2026.5.6 | 2026-07-02 |
| GHSA-wv26-j37q-2g7p | | OpenClaw's Slack plugin approvals used the exec approver gate for plugin actions | CWE-863 | 2026.5.12 | 2026-07-02 |
| GHSA-p2fh-f5fc-44hr | | OpenClaw: memory-wiki ingest could read local files with operator.write scope | CWE-732 | 2026.5.12 | 2026-07-02 |
| GHSA-qh2f-99mv-mrcf | | OpenClaw: Bundle MCP loopback could miss its exec denylist on session spawn | CWE-78, CWE-284 | 2026.5.12 | 2026-07-02 |
| GHSA-chm2-m3w2-wcxm | | OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch | CWE-290, CWE-863 | 2026.2.14 | 2026-02-17 |
| GHSA-h9h6-pwqv-j9hv | | Duplicate Advisory: Bootstrap token replay could widen pending pairing scopes | CWE-266 | — | 2026-06-16 |
| GHSA-8hj2-w4c9-fjfq | | Duplicate Advisory: BlueBubbles sender policy could match mutable conversation identifiers | CWE-807 | — | 2026-06-16 |
| GHSA-hc4w-hm59-9w88 | | Duplicate Advisory: Empty-scope device re-pairing could confuse caller scope containment | CWE-636 | — | 2026-06-16 |
| GHSA-r7vv-6763-m739 | | Duplicate Advisory: Skill-command dispatch could skip before-tool-call hooks | CWE-693 | — | 2026-06-16 |
| GHSA-wrr6-p5r6-474m | | Duplicate Advisory: Exec allowlist could miss side effects from transparent command wrappers | CWE-184 | — | 2026-06-16 |
| GHSA-6xcg-6q43-rj2v | | Duplicate Advisory: Exported session HTML could keep unsafe markdown links | CWE-83 | — | 2026-06-16 |
| GHSA-3wqp-prf6-2m72 | | OpenClaw: Feishu dynamic-agent bindings could miss configWrites enforcement | CWE-862 | 2026.5.6 | 2026-07-02 |
Repo-Only Advisories (44)
These advisories are visible on the repo security page but are not indexed in the GitHub Advisory Database (no npm package mapping). They cannot be fetched via the Advisory Database API.
| GHSA | Severity | Title | Published |
|---|---|---|---|
| GHSA-2q7j-2vhx-56g8 | | Feishu tools could ignore per-account disablement | 2026-06-30 |
| GHSA-2x93-h3hg-2xfp | | Browser snapshot routes could miss post-navigation SSRF checks | 2026-06-30 |
| GHSA-34mr-7r3m-gfg7 | | Exec allowlist glob matching could allow traversal bypasses | 2026-06-30 |
| GHSA-3fp5-v549-9v66 | | flock wrapper could bypass durable exec approval binding | 2026-06-30 |
| GHSA-3pmr-x9g8-m55r | | Discord guild actions could skip cross-provider requester authorization | 2026-06-30 |
| GHSA-3x84-qq85-fj65 | | Browser CDP discovery could accept blocked WebSocket URLs | 2026-06-30 |
| GHSA-4pqj-3c56-5fqq | | Workspace dotenv files could override provider credentials | 2026-06-30 |
| GHSA-52xj-c9p8-78cv | | MCP loopback could expose owner-only tools to non-owner runs | 2026-06-30 |
| GHSA-575v-8hfq-m3mc | | Sandbox bind mounts could bypass parent-directory denylist checks | 2026-06-30 |
| GHSA-724r-v4wf-mqc5 | | Hooks allowedAgentIds could be bypassed with blank agent IDs | 2026-06-30 |
| GHSA-7jx6-764p-fgg9 | | QQBot exec approvals could allow non-allowlisted senders | 2026-06-30 |
| GHSA-7vrr-rp4x-4g76 | | Plugin install commands could allow non-owner persistence | 2026-06-30 |
| GHSA-8f46-3xx3-8c9m | | Node exec approvals could use different gateway and node environments | 2026-06-30 |
| GHSA-8v95-qqcm-qp9h | | device.pair.approve could bypass role-management checks | 2026-06-30 |
| GHSA-9969-8g9h-rxwm | | Host exec environment filtering could allow Git ext transport | 2026-06-30 |
| GHSA-cf2p-f286-mphf | | Identity-bearing HTTP callers could reach admin-scoped tools | 2026-06-30 |
| GHSA-f6p7-6326-vf7v | | Discord moderation actions could miss trusted requester checks | 2026-06-30 |
| GHSA-fh38-965w-f6c3 | | WhatsApp group IDs could satisfy elevated sender allowlists | 2026-06-30 |
| GHSA-hjr6-g723-hmfm | | Host exec environment filtering could miss interpreter startup variables | 2026-06-30 |
| GHSA-hx85-fgcw-9vrc | | Device-pair approval could expose node system.run early | 2026-06-30 |
| GHSA-jhfx-v2j8-x3m6 | | OpenAI-compatible HTTP model overrides could miss admin authorization | 2026-06-30 |
| GHSA-m38g-vpwj-mpg9 | | OpenShell mirror sync could follow remote symlink parents | 2026-06-30 |
| GHSA-mgvr-6gvw-3rgr | | Sandbox exec-server HTTP requests could reach internal networks | 2026-06-30 |
| GHSA-mm9g-83wh-mhwj | | Isolated cron jobs could regain denied exec tools | 2026-06-30 |
| GHSA-p5xh-frrh-cmgj | | MS Teams message actions could miss requester authorization | 2026-06-30 |
| GHSA-rh6r-vvfc-86jq | | Setup-mode discovery could load untrusted workspace plugins | 2026-06-30 |
| GHSA-v7hx-r36p-f68m | | Message mutations could skip requester authorization | 2026-06-30 |
| GHSA-vr7j-7684-7gm5 | | HTTP Canvas responses could forge trusted A2UI actions | 2026-06-30 |
| GHSA-w8wf-3qvj-6xqf | | Feishu permission tools could ignore per-account disablement | 2026-06-30 |
| GHSA-wp73-f3gg-w4vr | | ClickClack agent-mode dispatch could ignore toolsAllow | 2026-06-30 |
| GHSA-wxh3-g47h-q3mc | | Host exec environment filtering could miss rustup startup variables | 2026-06-30 |
| GHSA-wxm8-ghhq-q688 | | MS Teams safeFetch could race DNS rebinding checks | 2026-06-30 |
| GHSA-x863-pqjw-hmgf | | Browser act route could miss current-tab URL checks | 2026-06-30 |
| GHSA-4xwj-mcc7-x7x5 | | Remote media URLs could slow-read exhaust tool workers | 2026-06-30 |
| GHSA-5p6w-wmh3-frfr | | WebSocket auth attempts could avoid non-browser rate limits | 2026-06-30 |
| GHSA-7w4v-g4m6-j88v | | [AgentGG] MS Teams allowFrom could bind to mutable display names | 2026-06-30 |
| GHSA-fh8v-vgcv-pwh4 | | ClickClack allowFrom could allow non-allowlisted commands | 2026-06-30 |
| GHSA-fwgr-fpv9-vf5x | | QQBot media upload could reach untrusted remote URLs | 2026-06-30 |
| GHSA-j4cx-jvq7-79vm | | Trajectory export could skip broad credential redaction | 2026-06-30 |
| GHSA-mhm4-93fw-4qr2 | | Skill command dispatch could skip effective tool policy | 2026-06-30 |
| GHSA-prwc-c6w5-mmgr | | Bot Framework serviceUrl validation could leak bot tokens | 2026-06-30 |
| GHSA-v4f6-x5g5-2g4g | | Native web search could ignore OpenClaw tool policy | 2026-06-30 |
| GHSA-v54h-q2vx-vgg4 | | MS Teams outbound requests could leak Bot Framework tokens | 2026-06-30 |
| GHSA-wgq8-x5wm-g4rw | | Plugin install wrappers could skip install policy | 2026-06-30 |
All OpenClaw CVEs by CNA — CVE List V5 (543)
Every CVE in CVEProject/cvelistV5 whose affected product is OpenClaw, regardless of assigner. 34 were project-issued (GitHub as CNA); 509 were assigned by third parties (overwhelmingly VulnCheck). Generated by reconcile_cnas.py; see cna-breakdown.json for aggregates.
| CVE | Assigning CNA | Published | State | In GHSA pipeline |
|---|---|---|---|---|
| CVE-2026-22168 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22169 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22170 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22171 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22172 | VulnCheck | 2026-03-20 | PUBLISHED | — |
| CVE-2026-22174 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22175 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22176 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-22177 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22178 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22179 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22180 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22181 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-22217 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-24763 | GitHub_M | 2026-02-02 | PUBLISHED | ✅ |
| CVE-2026-24764 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-25157 | GitHub_M | 2026-02-04 | PUBLISHED | ✅ |
| CVE-2026-25253 | mitre | 2026-02-01 | PUBLISHED | ✅ |
| CVE-2026-25474 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-25475 | GitHub_M | 2026-02-04 | PUBLISHED | — |
| CVE-2026-25593 | GitHub_M | 2026-02-06 | PUBLISHED | — |
| CVE-2026-26316 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26317 | GitHub_M | 2026-02-19 | PUBLISHED | ✅ |
| CVE-2026-26319 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26320 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26321 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26322 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26323 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26324 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26325 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26326 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26327 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26328 | GitHub_M | 2026-02-19 | PUBLISHED | ✅ |
| CVE-2026-26329 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-26972 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27001 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27002 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27003 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27004 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27007 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27008 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27009 | GitHub_M | 2026-02-19 | PUBLISHED | — |
| CVE-2026-27183 | VulnCheck | 2026-03-23 | PUBLISHED | — |
| CVE-2026-27484 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27485 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27486 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27487 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27488 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27522 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-27523 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-27524 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-27545 | VulnCheck | 2026-03-18 | PUBLISHED | — |
| CVE-2026-27566 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-27576 | GitHub_M | 2026-02-21 | PUBLISHED | — |
| CVE-2026-27646 | VulnCheck | 2026-03-23 | PUBLISHED | — |
| CVE-2026-27670 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-28363 | mitre | 2026-02-27 | PUBLISHED | — |
| CVE-2026-28391 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28392 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28393 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28394 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28395 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28446 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28447 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28448 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28449 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-28450 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28451 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28452 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-28453 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28454 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28456 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28457 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28458 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-28459 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28460 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-28461 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-28462 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28463 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28464 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28465 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28466 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28467 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28468 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28469 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-28470 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28471 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28472 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28473 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28474 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28475 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28476 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28477 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28478 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-28479 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28480 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-28481 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28482 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28485 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-28486 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-29606 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-29607 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-29608 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-29609 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-29610 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-29611 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-29612 | VulnCheck | 2026-03-05 | PUBLISHED | ✅ |
| CVE-2026-29613 | VulnCheck | 2026-03-05 | PUBLISHED | — |
| CVE-2026-31989 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31990 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31991 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31992 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31993 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31994 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31995 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31996 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31997 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31998 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-31999 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32000 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32001 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32002 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32003 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32004 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32005 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32006 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32007 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32008 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32009 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32010 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32011 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32013 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32014 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32015 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32016 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32017 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32018 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32019 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32020 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32021 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32022 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32023 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32024 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32025 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32026 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32027 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32028 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32029 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32030 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32031 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32032 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32033 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32034 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32035 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32036 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32037 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32038 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32039 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32040 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32041 | VulnCheck | 2026-03-19 | PUBLISHED | — |
| CVE-2026-32042 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32043 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32044 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32045 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32046 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32048 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32049 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32050 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32051 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32052 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32053 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32054 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32055 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32056 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32057 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32058 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32059 | VulnCheck | 2026-03-11 | PUBLISHED | — |
| CVE-2026-32060 | VulnCheck | 2026-03-11 | PUBLISHED | — |
| CVE-2026-32061 | VulnCheck | 2026-03-11 | PUBLISHED | — |
| CVE-2026-32062 | VulnCheck | 2026-03-11 | PUBLISHED | — |
| CVE-2026-32063 | VulnCheck | 2026-03-11 | PUBLISHED | — |
| CVE-2026-32064 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32065 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32067 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32302 | GitHub_M | 2026-03-12 | PUBLISHED | — |
| CVE-2026-32846 | VulnCheck | 2026-03-26 | PUBLISHED | — |
| CVE-2026-32895 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32896 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32897 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32898 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32899 | VulnCheck | 2026-03-21 | PUBLISHED | — |
| CVE-2026-32905 | VulnCheck | 2026-05-29 | PUBLISHED | — |
| CVE-2026-32906 | VulnCheck | 2026-05-29 | PUBLISHED | — |
| CVE-2026-32913 | VulnCheck | 2026-03-23 | PUBLISHED | — |
| CVE-2026-32914 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32915 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32916 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32917 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32918 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32919 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32920 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32921 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32922 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32923 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32924 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32970 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32971 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32972 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32973 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32974 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32975 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32976 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32977 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32978 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32979 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32980 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32982 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-32987 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-32988 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33572 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-33573 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-33574 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-33575 | VulnCheck | 2026-03-29 | PUBLISHED | — |
| CVE-2026-33576 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33577 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33578 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33579 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33580 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-33581 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-34425 | VulnCheck | 2026-04-02 | PUBLISHED | — |
| CVE-2026-34426 | VulnCheck | 2026-04-02 | PUBLISHED | — |
| CVE-2026-34503 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-34504 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-34505 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-34506 | VulnCheck | 2026-03-31 | PUBLISHED | — |
| CVE-2026-34507 | VulnCheck | 2026-05-29 | PUBLISHED | — |
| CVE-2026-34510 | VulnCheck | 2026-04-01 | PUBLISHED | — |
| CVE-2026-34511 | VulnCheck | 2026-04-03 | PUBLISHED | — |
| CVE-2026-34512 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35617 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35618 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35619 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35620 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35621 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35622 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35623 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35624 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35625 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35626 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35627 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35628 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35629 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35630 | VulnCheck | 2026-05-29 | PUBLISHED | ✅ |
| CVE-2026-35631 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35632 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35633 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35634 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35635 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35636 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35637 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35638 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35639 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35640 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35641 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35642 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35643 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35644 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35645 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35646 | VulnCheck | 2026-04-09 | PUBLISHED | — |
| CVE-2026-35647 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35648 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35649 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35650 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35651 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35652 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35653 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35654 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35655 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35656 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35657 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35658 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35659 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35660 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35661 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35662 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35663 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35664 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35665 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35666 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35667 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35668 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35669 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35670 | VulnCheck | 2026-04-10 | PUBLISHED | — |
| CVE-2026-35673 | VulnCheck | 2026-05-29 | PUBLISHED | — |
| CVE-2026-35674 | VulnCheck | 2026-05-29 | PUBLISHED | — |
| CVE-2026-3689 | zdi | 2026-04-11 | PUBLISHED | — |
| CVE-2026-3690 | zdi | 2026-04-11 | PUBLISHED | — |
| CVE-2026-3691 | zdi | 2026-04-11 | PUBLISHED | — |
| CVE-2026-40037 | VulnCheck | 2026-04-08 | PUBLISHED | — |
| CVE-2026-40045 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-4039 | VulDB | 2026-03-12 | PUBLISHED | — |
| CVE-2026-4040 | VulDB | 2026-03-12 | PUBLISHED | — |
| CVE-2026-41294 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41295 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41296 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41297 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41298 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41299 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41300 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41301 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41302 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41303 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41329 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41330 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41331 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41332 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41333 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41334 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41335 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41336 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41337 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41338 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41339 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41340 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41341 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41342 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41343 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41344 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41345 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41346 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41347 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41348 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41349 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41350 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41351 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41352 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41353 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41354 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41355 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41356 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41357 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41358 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41359 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41360 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41361 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41362 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41363 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41364 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41365 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41366 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41367 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41368 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41369 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41370 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41371 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41372 | VulnCheck | 2026-04-27 | PUBLISHED | — |
| CVE-2026-41373 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41374 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41375 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41376 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41377 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41378 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41379 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41380 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41381 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41382 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41383 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41384 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41385 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41386 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41387 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41388 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41389 | VulnCheck | 2026-04-20 | PUBLISHED | — |
| CVE-2026-41390 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41391 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41392 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41393 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41394 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41395 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41396 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41397 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41398 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41399 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41400 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41402 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41403 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41404 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41405 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41406 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41407 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41408 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41908 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41909 | VulnCheck | 2026-04-23 | PUBLISHED | — |
| CVE-2026-41910 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41911 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41912 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41913 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41914 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41915 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-41916 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42420 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42421 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42422 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42423 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42424 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42426 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42427 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42428 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42429 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42430 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42431 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42432 | VulnCheck | 2026-04-28 | PUBLISHED | — |
| CVE-2026-42433 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42434 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42435 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42436 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42437 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42438 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-42439 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43526 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43527 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43528 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43529 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43530 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43531 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43532 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43533 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43534 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43535 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43566 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43567 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43568 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43569 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43570 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43571 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43572 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43573 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43574 | VulnCheck | 2026-05-05 | PUBLISHED | — |
| CVE-2026-43575 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43576 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43577 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43578 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43579 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43580 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43581 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43582 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43583 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43584 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-43585 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44109 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44110 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44111 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44112 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44113 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44114 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44115 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44116 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44117 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44118 | VulnCheck | 2026-05-06 | PUBLISHED | — |
| CVE-2026-44991 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44992 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44993 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44994 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44995 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44996 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44997 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44998 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-44999 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45000 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45001 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45002 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45003 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45004 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45005 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45006 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45223 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-45224 | VulnCheck | 2026-05-11 | PUBLISHED | — |
| CVE-2026-53806 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53807 | VulnCheck | 2026-06-11 | PUBLISHED | — |
| CVE-2026-53808 | VulnCheck | 2026-06-11 | PUBLISHED | — |
| CVE-2026-53809 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53810 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53811 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53812 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53813 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53814 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53815 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53816 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53817 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53818 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53819 | VulnCheck | 2026-06-11 | PUBLISHED | ✅ |
| CVE-2026-53820 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53821 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53822 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53823 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53824 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53825 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53826 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53827 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53828 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53829 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53830 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53831 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53832 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53833 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53834 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53835 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53836 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53837 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53838 | VulnCheck | 2026-06-12 | PUBLISHED | ✅ |
| CVE-2026-53839 | VulnCheck | 2026-06-12 | PUBLISHED | — |
| CVE-2026-53840 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53841 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53842 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53843 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53844 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53845 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53846 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53847 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53848 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53849 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53850 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53851 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53852 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53853 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53854 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53855 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53856 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53857 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53858 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53859 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53860 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53861 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53862 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53863 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53864 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53865 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-53866 | VulnCheck | 2026-06-16 | PUBLISHED | ✅ |
| CVE-2026-6011 | VulDB | 2026-04-10 | PUBLISHED | — |
| CVE-2026-8305 | VulDB | 2026-05-11 | PUBLISHED | — |
| CVE-2026-8621 | VulnCheck | 2026-05-14 | PUBLISHED | — |
| CVE-2026-8629 | VulnCheck | 2026-05-14 | PUBLISHED | — |
| CVE-2026-8634 | VulnCheck | 2026-05-14 | PUBLISHED | — |
CVE Publication Pipeline Status
| CVE ID | State | In cvelistV5 | GHSA Published | CNA |
|---|---|---|---|---|
| CVE-2026-24763 | ✅ PUBLISHED | ✅ | 2026-02-02 | GitHub_M |
| CVE-2026-25157 | ✅ PUBLISHED | ✅ | 2026-02-02 | GitHub_M |
| CVE-2026-25253 | ✅ PUBLISHED | ✅ | 2026-02-02 | mitre |
| CVE-2026-26317 | ✅ PUBLISHED | ✅ | 2026-02-18 | GitHub_M |
| CVE-2026-26328 | ✅ PUBLISHED | ✅ | 2026-02-18 | GitHub_M |
| CVE-2026-28452 | ✅ PUBLISHED | ✅ | 2026-02-18 | VulnCheck |
| CVE-2026-28458 | ✅ PUBLISHED | ✅ | 2026-02-17 | VulnCheck |
| CVE-2026-28469 | ✅ PUBLISHED | ✅ | 2026-02-18 | VulnCheck |
| CVE-2026-28478 | ✅ PUBLISHED | ✅ | 2026-02-18 | VulnCheck |
| CVE-2026-28480 | ✅ PUBLISHED | ✅ | 2026-02-18 | VulnCheck |
| CVE-2026-29612 | ✅ PUBLISHED | ✅ | 2026-02-18 | VulnCheck |
| CVE-2026-35630 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53806 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53809 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53810 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53811 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53812 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53813 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53814 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53815 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53816 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53817 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53818 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53819 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53830 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53831 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53832 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53833 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53834 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53836 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53837 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53838 | ✅ PUBLISHED | ✅ | 2026-07-02 | VulnCheck |
| CVE-2026-53840 | ✅ PUBLISHED | ✅ | 2026-06-17 | VulnCheck |
| CVE-2026-53841 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53842 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53843 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53844 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53845 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53846 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53847 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53848 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53849 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53850 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53851 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53852 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53853 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53854 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53855 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53856 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53857 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53858 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53859 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53860 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53861 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53862 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53863 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53864 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53865 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
| CVE-2026-53866 | ✅ PUBLISHED | ✅ | 2026-06-18 | VulnCheck |
Auto-generated by update_readme.py — see README.md for the dashboard view.