CVE-2026-40070
Forge identity certificates via unverified signatures in BSV Ruby SDK.
Is CVE-2026-40070 being exploited?
Not confirmed. CVE-2026-40070 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-40070?
CVE-2026-40070 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-40070?
Yes. A fix has been recorded for CVE-2026-40070. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40070 affect?
CVE-2026-40070 affects BSV Ruby SDK (WalletClient#acquire_certificate) v0.3.1–0.8.1, BSV certifier API endpoints (acquire_certificate, issuance path). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40070?
Upgrade to 0.8.2+; enable cert verification; rotate affected certs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Impersonation via forged identity certificates through API paths; bypasses identity checks.
Patch when possible
- affected>= 0.3.1 and < 0.8.2
- affected>= 0.3.1 and < 0.8.2
- affected>= 0.1.2 and < 0.3.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.