CVE-2026-40070

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.3.1 to before 0.8.2, BSV::Wallet::WalletClient#acquire_certificate persists certificate records to storage without verifying the certifier's signature over the certificate contents. In acquisition_protocol: 'direct', the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. In acquisition_protocol: 'issuance', the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification. An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to list_certificates and prove_certificate.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 9, 2026

Last Modified

April 24, 2026

Advisory Details (5)

Auto-updated May 6, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths) · Advisory · sgbett/bsv-ruby-sdk · GitHub

https://github.com/sgbett/bsv-ruby-sdk/security/advisories/GHSA-hc36-c89j-5f4j
Web page

fix(security): A1 security hotfixes (bsv-sdk 0.8.2 + bsv-wallet 0.3.4) — closes #305 by sgbett · Pull Request #306 · sgbett/bsv-ruby-sdk · GitHub

https://github.com/sgbett/bsv-ruby-sdk/pull/306
Web page

[HLR] A1 — Security hotfixes for bsv-sdk 0.8.2 + bsv-wallet 0.3.4 (post-compliance-review) · Issue #305 · sgbett/bsv-ruby-sdk · GitHub

https://github.com/sgbett/bsv-ruby-sdk/issues/305
Web page

Merge pull request #306 from sgbett/fix/305-security-hotfixes · sgbett/bsv-ruby-sdk@4992e8a · GitHub

https://github.com/sgbett/bsv-ruby-sdk/commit/4992e8a265fd914a7eeb0405c69d1ff0122a84cc
Web page

Identity Certificates | BRC

https://brc.dev/52

Affected Packages

(2 across 1 ecosystem)
RubyGems(2)
PackageVulnerable rangeFix by version rangeDependents
bsv-sdk0.3.1 ... 0.8.1 (10 versions)
  • 0.3.1 up to 0.8.2: fixed in 0.8.2
—
bsv-wallet0.1.2 ... 0.3.3 (8 versions)
  • 0.1.2 up to 0.3.4: fixed in 0.3.4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 178 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-18 03:43 UTCEG score recompute
  6. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-17 14:56 UTCEG score recompute
  8. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-12 16:09 UTCEG score recompute
  13. 2026-10-11 19:52 UTCEG score recompute
  14. 2026-10-11 17:05 UTCEG score recompute
  15. 2026-10-11 14:32 UTCEG score recompute
  16. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-10 21:23 UTCOSV refresh
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 71 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-09-21 09:19 UTCOSV refresh
  6. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-09-02 07:44 UTCOSV refresh
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-08-16 07:10 UTCEG score recompute
  37. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-08-14 05:08 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-08-12 19:24 UTCEG score recompute
  42. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-11 03:01 UTCEG score recompute
  44. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-09 15:59 UTCEG score recompute
  46. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-09 04:34 UTCEG score recompute
  48. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-08 01:54 UTCEG score recompute
  50. 2026-08-07 14:29 UTCEG score recompute
  51. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-05 23:45 UTCEG score recompute
  53. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-08-03 22:00 UTCEG score recompute
  57. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-02 13:55 UTCEG score recompute
  59. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-07-23 03:10 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  70. 2026-07-20 20:32 UTCOSV refresh
  71. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same product + same CWE)

Same product

1 shown

RubyGems:bsv-sdk

Frequently asked(5)

What is CVE-2026-40070?
CVE-2026-40070 is a high-severity vulnerability; its CVE record was published on April 9, 2026. BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.3.1 to before 0.8.2, BSV::Wallet::WalletClient#acquirecertificate persists certificate records to storage without verifying the certifier's signature over the certificate contents. In acquisitionprotocol: 'direct', the caller supplies all…
When was the CVE record for CVE-2026-40070 published?
The CVE record for CVE-2026-40070 was published on April 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 24, 2026; the record at its source may have been updated since.
Is CVE-2026-40070 actively exploited?
CVE-2026-40070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40070?
CVE-2026-40070 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-40070?
A fix for CVE-2026-40070 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40070

Explore →

Is Your Infrastructure Affected by CVE-2026-40070?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs