Quick answers
- Is CVE-2026-78062 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78062 being exploited in the wild.
- How severe is CVE-2026-78062?
- High severity, with a CVSS score of 7.3, published 23 August 2026.
- Which products and versions are affected?
- Vas3k TaxHacker up to 0.8.2.
- Is there a fix for CVE-2026-78062?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78062 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-78062?
- Check whether you run Vas3k TaxHacker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a hardcoded credential weakness (CWE-798) in the JWT secret handler component. The Zod schema in lib/config.ts defines BETTER_AUTH_SECRET with a weak default value 'please-set-your-key-here' (only 24 characters, below the 16-character minimum) that is used as the JWT signing key when the environment variable is not explicitly set. An unauthenticated remote attacker can forge valid JWT session tokens using the known default secret and HS256 algorithm, then use these tokens to bypass authentication and impersonate any user. The attack requires no user interaction or special privileges; it only requires network access to the application. No patch has been confirmed as available at the time of disclosure.
Affected products
- vas3k TaxHacker up to 0.8.2
Timeline
- 2026-08-23: disclosed: Published on NVD
- 2026-07-07: other: Security issue reported on GitHub (#147)