B42/100
Security incident · checklist estimated
Bun v1.4.5 security release
Tier B · Patch this week – Put it in the sprint
Tier B because: Full takeover OR secrets exposed OR supply chain
Reach
Attack
Damage
Fix
Full takeover
What to do
- Upgrade to Bun v1.4.5
The Brief
- Bun v1.4.5 is released as a security release.
- The release updates lsquic, c-ares, SQLite, llhttp and BoringSSL.
- The source does not list specific CVEs, severity or exploitation details.
Why it matters
Bun users receive security fixes from updated bundled dependencies, so running the new release reduces exposure to the issues they address.
The checklist behind the tier
Checklist · 2 of 10 yes · estimated from older data, not yet checked against the sources
| Yes | Hits tech teams | Does it affect software, devices or services that developers, ops or IT teams build with, run or are responsible for? |
| No | Core infrastructure | Is the flaw in, or the compromise of, software that nearly every team runs? |
| No | Popular tool | Is the flaw in, or the compromise of, a widely used framework, tool, platform, OS or package? |
| No | Exploited in the wild | Do sources report real attacks using it? |
| No | Public exploit | Is a working exploit or detailed proof-of-concept public? |
| No | Remote, no login | Can an attacker use it over the network without credentials or user interaction? |
| Yes | Full takeover | Does it lead to code execution, root/admin rights or full account takeover? |
| No | Secrets exposed | Were credentials, tokens, keys, configs, source code or customer data stolen or exposed? |
| No | Supply chain | Was malicious code shipped through a channel developers trust? |
| No | No fix yet | Is there no patched version yet? |
Timeline
Source
Bun v1.4.5 ↗ bun.com · 3h ago
First seen · 1 source · Full story page · How tiers are decided