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.
CVE-2026-78062
This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(low)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 23, 2026
Last Modified
August 23, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026GitHub - vas3k/TaxHacker: Self-hosted AI accounting app. LLM analyzer for receipts, invoices, transactions with custom prompts and categories · GitHub
https://github.com/vas3k/TaxHacker/[Security] Hardcoded Default JWT Secret Leads to Authentication Bypass · Issue #147 · vas3k/TaxHacker · GitHub
https://github.com/vas3k/TaxHacker/issues/147Vendor Advisories for CVE-2026-78062(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-23 05:19 UTCEG score recompute
- 2026-08-23 05:18 UTCNVD updateCVSS v4 → 5.5
- 2026-08-23 04:24 UTCEG score recompute
- 2026-08-23 04:23 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-78062?
When was CVE-2026-78062 disclosed?
What is the CVSS score of CVE-2026-78062?
How do I remediate CVE-2026-78062?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78062
Is Your Infrastructure Affected by CVE-2026-78062?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.