# CVE-2026-78062: vas3k TaxHacker JWT Secret config.ts envSchema.parse hard-coded credentials

> Hard-coded JWT secret in vas3k TaxHacker allows remote attackers to bypass authentication and potentially take over accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-c2p7-hcxm-xqhj

## What is CVE-2026-78062?

CVE-2026-78062 is a medium-severity vulnerability in vas3k TaxHacker, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in vas3k TaxHacker up to 0.8.2. The affected element is the function envSchema.parse of the file lib/config.ts of the component JWT Secret Handler. The manipulation of the argument BETTER_AUTH_SECRET leads to hard-coded credentials. The attack can be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2026-78062?


## How do I fix CVE-2026-78062?

No fix has been published for CVE-2026-78062 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78062 being exploited?

There is no known exploitation of CVE-2026-78062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78062 and fix it if it is affected.

What it is: CVE-2026-78062 is a medium-severity vulnerability in vas3k TaxHacker, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78062 in the wild and no public exploit code.

Affected product: vas3k TaxHacker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78062/ (Markdown: https://insights.sbomify.com/CVE-2026-78062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78062
- OSV: https://osv.dev/vulnerability/CVE-2026-78062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78062/
Summaries are generated and may contain mistakes; the official description above is the record.