Every advisory below is published and credited. Reports still in coordinated disclosure are not listed, named or hinted at until the maintainer publishes them.
29
Every entry is published and credited. Ordered by CVSS base score. Each row opens to the base vector in plain language, what to do, and how long disclosure took.
| NR | Advisory | Package | CVSS | Severity | Weakness | CWE | Base vector | Published |
|---|---|---|---|---|---|---|---|---|
| 01 | CVE-2026-130169 | autogpt-platform-beta | 10.0 | Critical | Authentication bypass | 287 | v3.1AVNACLPRNUINSCCHIHAH | 2026-10-05 |
Anyone who can reach it over the network, with no account and no user interaction, can read and change sensitive data and make it unavailable, and the impact reaches beyond the vulnerable component. What to doUpgrade to 0.8.0 Published2026-10-05Published by the maintainer Read the writeup → | ||||||||
| 02 | GHSA-42mf-vpmr-gw5r | ag2 | 9.9 | Critical | Command injection | 78 | v3.1AVNACLPRLUINSCCHIHAH | 2026-10-03 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read and change sensitive data and make it unavailable, and the impact reaches beyond the vulnerable component. Score is my assessment; GitHub published no CVSS for this advisory. What to doUpgrade to 1.1.2 Report to publication134 daysReported privately 2026-05-22, published 2026-10-03 Read the writeup → | ||||||||
| 03 | CVE-2026-49950 | xinference | 9.3 | Critical | Missing authentication | 306 | v4.0AVNACLATNPRNUINVCHVIHVAHSCNSINSAN | 2026-10-16 |
Anyone who can reach it over the network, with no account and no user interaction, can read and change sensitive data and make it unavailable. What to doNo fix listed Published2026-10-16Published by the maintainer Read the writeup → | ||||||||
| 04 | GHSA-hxvp-ff3g-qcj7 | @vendure/core | 8.8 | High | Information disclosure | 200 | v3.1AVNACLPRLUINSUCHIHAH | 2026-10-23 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read and change sensitive data and make it unavailable. What to doNo fix listed Report to publication19 daysReported privately 2026-10-04, published 2026-10-23 Read the writeup → | ||||||||
| 05 | GHSA-v3vj-mch3-x6c2 | omnigent | 8.8 | High | Resource exposure | 668 | v3.1AVLACLPRLUINSCCHIHAH | 2026-10-13 |
Someone with local access, with a low-privilege account and no user interaction, can read and change sensitive data and make it unavailable, and the impact reaches beyond the vulnerable component. What to doUpgrade to 0.18.0 Report to publication59 daysReported privately 2026-08-15, published 2026-10-13 Read the writeup → | ||||||||
| 06 | GHSA-5mc6-2qfj-59cg | opik | 8.8 | High | Code injection | 94 | v3.1AVNACLPRNUIRSUCHIHAH | 2026-11-05 |
Anyone who can reach it over the network, with no account, if a user takes some action, can read and change sensitive data and make it unavailable. What to doFix differs by range Report to publication11 daysReported privately 2026-10-25, published 2026-11-05 Read the writeup → | ||||||||
| 07 | CVE-2026-57516 | ray | 8.8 | High | Code injection | 94 | v3.1AVNACLPRNUIRSUCHIHAH | 2026-07-01 |
Anyone who can reach it over the network, with no account, if a user takes some action, can read and change sensitive data and make it unavailable. What to doUpgrade to 2.56.0 Published2026-07-01Published by the maintainer Read the writeup → | ||||||||
| 08 | GHSA-jmr9-98g4-2phv | github.com/ | 8.7 | High | Access control | 284 | v4.0AVNACLATNPRLUINVCHVIHVAHSCNSINSAN | 2026-10-08 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read and change sensitive data and make it unavailable. What to doFix differs by range Published2026-10-08Published by the maintainer Read the writeup → | ||||||||
| 09 | CVE-2026-132257 | autogpt-platform-beta | 8.2 | High | Hard-coded crypto key | 321 | v3.1AVNACHPRLUINSCCHIHAN | 2026-10-05 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, given conditions outside the attacker's control, can read and change sensitive data, and the impact reaches beyond the vulnerable component. What to doUpgrade to 0.8.0 Published2026-10-05Published by the maintainer Read the writeup → | ||||||||
| 10 | GHSA-qrjx-72xx-xhmh | ag2 | 8.1 | High | Path traversal | 22 | v3.1AVNACLPRLUINSUCHIHAN | 2026-09-25 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read and change sensitive data. Score is my assessment; GitHub published no CVSS for this advisory. What to doFix differs by range Report to publication126 daysReported privately 2026-05-22, published 2026-09-25 Read the writeup → | ||||||||
| 11 | CVE-2026-45675 | open-webui | 8.1 | High | Privilege escalation | 269 | v3.1AVNACHPRNUINSUCHIHAH | 2026-05-11 |
Anyone who can reach it over the network, with no account and no user interaction, given conditions outside the attacker's control, can read and change sensitive data and make it unavailable. What to doUpgrade to 0.9.0 Report to publication34 daysReported privately 2026-04-07, published 2026-05-11 Read the writeup → | ||||||||
| 12 | GHSA-pqxw-g93w-hj9x | trigger.dev | 8.1 | High | Improper isolation | 653 | v4.0AVNACHATNPRNUINVCHVIHVANSCNSINSANEP | 2026-07-21 |
Anyone who can reach it over the network, with no account and no user interaction, if they can defeat a protection or obtain a target-specific secret, can read and change sensitive data. What to doUpgrade to 4.5.6 Report to publication60 daysReported privately 2026-05-22, published 2026-07-21 Read the writeup → | ||||||||
| 13 | GHSA-jc26-22qp-cgqj | trigger.dev | 7.9 | High | Missing authentication | 306 | v3.1AVAACHPRLUINSCCHIHAL | 2026-09-14 |
Anyone on an adjacent network, with a low-privilege account and no user interaction, given conditions outside the attacker's control, can read and change sensitive data and degrade its availability, and the impact reaches beyond the vulnerable component. What to doFix unclear Report to publication115 daysReported privately 2026-05-22, published 2026-09-14 Read the writeup → | ||||||||
| 14 | GHSA-3c52-v5v2-3r56 | budibase | 7.7 | High | Server side request forgery | 918 | v3.1AVNACLPRLUINSCCHINAN | 2026-09-17 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data, and the impact reaches beyond the vulnerable component. What to doUpgrade past 3.41.0 Report to publication118 daysReported privately 2026-05-22, published 2026-09-17 Read the writeup → | ||||||||
| 15 | CVE-2026-56673 | ComfyUI | 7.5 | High | Path traversal | 22 | v3.1AVNACLPRNUINSUCHINAN | 2026-07-15 |
Anyone who can reach it over the network, with no account and no user interaction, can read sensitive data. What to doUpgrade to 0.28.0 Published2026-07-15Published by the maintainer Read the writeup → | ||||||||
| 16 | CVE-2026-56671 | ComfyUI | 7.5 | High | Path traversal | 22 | v3.1AVNACLPRNUINSUCHINAN | 2026-07-15 |
Anyone who can reach it over the network, with no account and no user interaction, can read sensitive data. What to doUpgrade to 0.28.0 Published2026-07-15Published by the maintainer Read the writeup → | ||||||||
| 17 | CVE-2026-59714 | open-webui | 7.1 | High | Missing authorization | 862 | v3.1AVNACLPRLUINSUCNIHAL | 2026-07-02 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can change data with serious effect and degrade its availability. What to doUpgrade to 0.10.0 Report to publication49 daysReported privately 2026-05-14, published 2026-07-02 Read the writeup → | ||||||||
| 18 | GHSA-w677-p6hx-85vw | teableio/teable | 7.1 | High | Authentication bypass | 287 | v3.1AVNACLPRLUINSUCHILAN | 2026-10-13 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data and change some data. What to doUpgrade to release.2026-10-12T12-45-53Z.3331 Report to publication38 daysReported privately 2026-09-05, published 2026-10-13 Read the writeup → | ||||||||
| 19 | GHSA-8p4j-2mm9-rh78 | Tracecat | 6.5 | Medium | Server side request forgery | 918 | v3.1AVNACLPRLUINSUCHINAN | 2026-09-20 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data. What to doUpgrade to 1.0.0-beta.52-rc.3 Report to publication115 daysReported privately 2026-05-28, published 2026-09-20 Read the writeup → | ||||||||
| 20 | CVE-2026-53577 | io.kestra:kestra | 6.5 | Medium | Incorrect authorization | 863 | v3.1AVNACLPRLUINSUCHINAN | 2026-06-03 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data. What to doFixed in 1.0.45 or 1.3.21 Report to publication12 daysReported privately 2026-05-22, published 2026-06-03 Read the writeup → | ||||||||
| 21 | GHSA-jcc2-3vff-7867 | nocodb | 6.5 | Medium | CWE-522 | 522 | v3.1AVNACLPRLUINSUCHINAN | 2026-11-02 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data. What to doUpgrade to 2026.10.1 Published2026-11-02Published by the maintainer Read the writeup → | ||||||||
| 22 | GHSA-jvm6-86c5-f8j8 | teableio/teable | 6.5 | Medium | Server side request forgery | 918 | v3.1AVNACLPRLUINSUCHINAN | 2026-10-13 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data. What to doUpgrade to release.2026-10-12T12-45-53Z.3331 Report to publication39 daysReported privately 2026-09-04, published 2026-10-13 Read the writeup → | ||||||||
| 23 | CVE-2026-63342 | github.com/ | 6.3 | Medium | Incorrect authorization | 863 | v3.1AVNACHPRLUINSCCHINAN | 2026-06-30 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, given conditions outside the attacker's control, can read sensitive data, and the impact reaches beyond the vulnerable component. What to doUpgrade to 0.91.1 Report to publication39 daysReported privately 2026-05-22, published 2026-06-30 Read the writeup → | ||||||||
| 24 | GHSA-59h8-w5q6-mfmp | trigger.dev | 5.3 | Medium | Missing authentication | 306 | v3.1AVNACLPRNUINSUCNILAN | 2026-07-21 |
Anyone who can reach it over the network, with no account and no user interaction, can change some data. What to doUpgrade to 4.5.5 Report to publication60 daysReported privately 2026-05-22, published 2026-07-21 Read the writeup → | ||||||||
| 25 | CVE-2026-73301 | @budibase/server | 4.3 | Medium | Missing authorization | 862 | v3.1AVNACLPRLUINSUCLINAN | 2026-07-22 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read some data. What to doNo fix listed Report to publication61 daysReported privately 2026-05-22, published 2026-07-22 Read the writeup → | ||||||||
| 26 | GHSA-64mc-4p6f-r7x9 | vaultwarden | 4.3 | Medium | Incorrect authorization | 863 | v3.1AVNACLPRLUINSUCLINAN | 2026-10-28 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read some data. What to doUpgrade to 1.37.4 Report to publication41 daysReported privately 2026-09-17, published 2026-10-28 Read the writeup → | ||||||||
| 27 | GHSA-xf86-hfpm-92xr | directus | 3.1 | Low | Incorrect authorization | 863 | v3.1AVNACHPRLUINSUCLINAN | 2026-10-19 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, given conditions outside the attacker's control, can read some data. What to doUpgrade to 12.3.0 Report to publication150 daysReported privately 2026-05-22, published 2026-10-19 Read the writeup → | ||||||||
| 28 | CVE-2026-59715 | open-webui | 3.1 | Low | Missing authentication | 306 | v3.1AVNACHPRLUINSUCNILAN | 2026-07-02 |
Anyone who can reach it over the network, with a low-privilege account and no user interaction, given conditions outside the attacker's control, can change some data. What to doUpgrade to 0.10.0 Report to publication86 daysReported privately 2026-04-07, published 2026-07-02 Read the writeup → | ||||||||
| 29 | GHSA-jmgj-cq6g-6hr2 | nocodb | 2.7 | Low | Incorrect authorization | 863 | v3.1AVNACLPRHUINSUCNILAN | 2026-11-02 |
Anyone who can reach it over the network, with a high-privilege account and no user interaction, can change some data. What to doUpgrade to 2026.09.1 Report to publication39 daysReported privately 2026-09-24, published 2026-11-02 Read the writeup → | ||||||||
Every entry regenerates daily from the GitHub Advisory Database, so this list only ever shows work that is published and credited.