CVE-2026-4931
Marginal V1-core vulnerability
- Published7 Apr 2026
Description
Smart contract Marginal v1 performs unsafe downcast, allowing attackers to settle a large debt position for a negligible asset cost.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:NAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://cvefeed.io/cwe/detail/cwe-681-incorrect-conversion-between-numeric-types
- https://github.com/MarginalProtocol
- https://marginal.gitbook.io/docs
- https://medium.com/@clarkcorrin/cve-2026-4931-how-spearbits-cantina-denied-a-critical-vulnerability-using-verifiably-false-0a27b92ac2db
- https://scs.owasp.org/SCWE/SCSVS-CODE/SCWE-041/
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-4931 being actively exploited?
CVE-2026-4931 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.46%.
How severe is CVE-2026-4931?
CVE-2026-4931 has a CVSS 3.1 base score of 8.6, rated high. EPSS estimates a 0.46% probability of exploitation.
Which products are affected by CVE-2026-4931?
Affected products include Marginal V1-core.
How do I fix CVE-2026-4931?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-4931 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.