CVE-2024-58131: FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed
CVE-2024-58131 is a medium-severity flaw (CVSS 4.0) affecting fisco-bcos. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed when a malicious node (that has modified the codebase to allow a large min_seal_time value) joins a blockchain network.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-58131?
fisco-bcos: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2024-58131 being exploited?
CVE-2024-58131 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-58131 affect?
CVE-2024-58131 affects fisco-bcos. Severity is medium (CVSS 4.0). FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed when a malicious node (that has modified the codebase to allow a large min_seal_time value) joins a blockchain network.
How urgent is CVE-2024-58131?
Priority 29/100. Public exploit reference; Remotely exploitable, no login, no user action