CVE-2025-68435 json
Zerobyte has Authentication Bypass by Primary Weakness
published 10mo ago modified 4mo ago also EUVD-2025-204006
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.
Patch / fix
- nicotsx zerobyte 0.18.5
Is CVE-2025-68435 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 10mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- nicotsx zerobyte
Classification
- Weakness
-
- CWE-305 Authentication Bypass by Primary Weakness
References
-
github.com
/nicotsx/zerobyte/commit/13e080a18967705bd2b4e110e5f7693fdca1c692
patch
-
github.com
/nicotsx/zerobyte/security/advisories/GHSA-x539-c98q-38gv
mitigation, patch, vendor-advisory
-
github.com
/nicotsx/zerobyte/issues/161
issue-tracking
Sources
- CVE List CVE-2025-68435
- NVD CVE-2025-68435
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.