Account takeover via brute-forced JWT signing secret
Published May 14, 2026 · Updated May 14, 2026
Weak JWT signing in Enchanted Code Note Mark before 0.19.4 allows remote attackers to take over accounts by forging tokens. Base64Decoded.UnmarshalText decodes JWT_SECRET without validating that the resulting HS256 key is at least 32 bytes, and auth.go signs tokens with that key. Exploitation requires a deployed secret shorter than 32 bytes and one valid token to crack offline; a forged token authenticates as any user, including an administrator.
Summary
What happened
Weak JWT signing in Enchanted Code Note Mark before 0.19.4 allows remote attackers to take over accounts by forging tokens. Base64Decoded.UnmarshalText decodes JWT_SECRET without validating that the resulting HS256 key is at least 32 bytes, and auth.go signs tokens with that key. Exploitation requires a deployed secret shorter than 32 bytes and one valid token to crack offline; a forged token authenticates as any user, including an administrator.
The record
- CVE
- CVE-2026-44523
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- Enchanted Code
- Product
- Note Mark
- Classifications
- CWE-345, CWE-326, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.19.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory JWT-forgery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo