← Back
CVE-2026-50146
high
CVSS 7.1
Vulnerability in astro (CVE-2026-50146)
Summary
vulnerability in astro (CVE-2026-50146). Data can be tampered with by attackers. Exploitable via ``astro.config.mjs``. Mitigation: upgrade to `6.3.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-50146** has been found in astro.
Attackers can target a specific entry point like ``astro.config.mjs`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade astro to **6.3.3** or later.
If unsure, ask your IT team or search "astro CVE-2026-50146" on the vendor's site.
CVE-2026-50146 (astro) — CWE-80 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `astro.config.mjs`
Patched: `6.3.3` — 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-80) exists in astro. Attackers reach the vulnerable code path via ``astro.config.mjs`` without authentication.
📍 Affected scope
astro — . Attack surface: `astro.config.mjs`.
🔥 Severity
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **6.3.3**.
🛡️ 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 'astro' .` 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 'astro' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `astro` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade astro to 6.3.3ステージング環境で 6.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
astro
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.3.3"}]}]