← Back
CVE-2026-59728
medium
CVSS 4.3
Vulnerability in @astrojs/rss (CVE-2026-59728)
Summary
vulnerability in @astrojs/rss (CVE-2026-59728). Risk of unauthorized operations or information disclosure. Exploitable via ``source.title``. Mitigation: upgrade to `4.0.19` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59728** has been found in @astrojs/rss.
Attackers can target a specific entry point like ``source.title`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @astrojs/rss to **4.0.19** or later.
If unsure, ask your IT team or search "@astrojs/rss CVE-2026-59728" on the vendor's site.
CVE-2026-59728 (@astrojs/rss) — CWE-91 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `source.title` / `enclosure.type` / `RSSFeedItem`
Patched: `4.0.19` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-91) exists in @astrojs/rss. Attackers reach the vulnerable code path via ``source.title`` without authentication.
📍 Affected scope
@astrojs/rss — . Attack surface: `source.title` / `enclosure.type` / `RSSFeedItem`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.0.19**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@astrojs/rss' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@astrojs/rss' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@astrojs/rss` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @astrojs/rss to 4.0.19ステージング環境で 4.0.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@astrojs/rss
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.19"}]}]
References
- web https://github.com/withastro/astro/security/advisories/GHSA-8j5q-mfj2-5q9q
- web https://github.com/withastro/astro/pull/17209
- web https://github.com/withastro/astro/commit/fbcfa039dfe3d700b239f595a6c55ee35e45bd06
- web https://github.com/withastro/astro/releases/tag/@astrojs/[email protected]
- web https://github.com/advisories/GHSA-8j5q-mfj2-5q9q
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59728