cve.bz

CVE-2026-64682 AstroBlocks: Admin session tokens can be forged due to a hard-coded fallback JWT secret and a mismatched environment variable name

9.8 criticalEPSS 0.6%

Critical (9.8) in nauelg astro-blocks. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
AstroBlocks is a block-first CMS for Astro projects. Prior to version 3.4.0, admin session tokens can be forged due to a hard-coded fallback JWT secret and a mismatched environment variable name. An attacker who knows the public fallback value (readable in the published package) can forge a valid session token with role: "owner" and obtain full administrative control of the CMS — creating/deleting content, users, media, redirects, and configuration. This issue has been patched in version 3.4.0.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-321 Use of Hard-coded Cryptographic Key
CWE-798 Use of Hard-coded Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-64682 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64682?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64682?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64682 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-64682

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-64682](https://cve.bz/cve/badge/CVE-2026-64682.svg)](https://cve.bz/cve/CVE-2026-64682)

HTML:

<a href="https://cve.bz/cve/CVE-2026-64682"><img src="https://cve.bz/cve/badge/CVE-2026-64682.svg" alt="CVE-2026-64682"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
NauelG astro-blocks< 3.4.0

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON