Remote code execution in examplelib
- npm/examplelib
- <1.2.3
- fixed in 1.2.3
- >=2.0.0 <2.0.5
- fixed in 2.0.5
Exploited vulnerabilities, weekly
A small, human-reviewed feed of what attackers are actually using, for engineers on call and for the coding agents working next to them. Each record names the package, the affected versions and the first safe version.
$ curl -s ziro.sh/feed.json \
| jq '.data[0] | {id, affects}'
{
"id": "CVE-0000-0000",
"affects": [{
"ecosystem": "npm",
"package": "examplelib",
"ranges": ["<1.2.3"],
"fixed": ["1.2.3"]
}]
}
$ 01 / Feed
2026-44, Oct 26–Nov 1, 2026
Nothing published for week 2026-44 yet.
The feed goes live after a two-week private review run. Every record is checked by a person against at least two sources before it appears here, in feed.json and in RSS.
This is the shape each record will take: the vulnerable range, then the version that fixes it.
02 / Agents
Everything here is a static file. Point your agent at llms.txt, poll the JSON, or ask any page for Markdown with Accept: text/markdown.
curl -s https://ziro.sh/feed.json | jq '.data[] | {id, affects}'03 / Rule
A vulnerability enters the feed when any of these is true. Everything else, including most CVEs, stays out.
Sources: CISA KEV, OSV.dev, GitHub Security Advisories, NVD, FIRST EPSS and vendor advisories. How records are made.