CVE-2026-3407Disclosure

LOWCVSS 1.9 · LOW

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

A vulnerability was determined in YosysHQ yosys up to 0.62. This affects the function Yosys::RTLIL::Const::set of the file kernel/rtlil.h of the component BLIF File Parser. This manipulation causes heap-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. Applying a patch is the recommended action to fix this issue. It appears that the issue is not reproducible all the time.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-119CWE-122

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-03-02: 2Technical Details · 2026-03-02: 203-02
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
By indicator
Full discourse2 posts
  • CyberDudeBivash® | Global Cybersecurity Company@cyberbivash
    Disclosure

    🚨 CYBERDUDEBIVASH SENTINEL APEX ALERT 🚨 Threat: CVE-2026-3407 - YosysHQ yosys BLIF File rtlil.h set heap-based overflow Intel Report: https://ift.tt/RQ4KB68

    Post summary

    Intel reports a new heap‑based overflow vulnerability (CVE‑2026‑3407) in YosysHQ yosys BLIF File rtlil.h.

    0000043
    342 followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-3407 Heap-Based Buffer Overflow in YosysHQ Yosys BLIF File Parser up to 0.62 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-3407

    Post summary

    A heap‑based buffer overflow vulnerability has been disclosed in YosysHQ Yosys BLIF File Parser up to version 0.62, with no evidence of exploitation or mitigation mentioned.

    0000068
    4.0K followersView on X

Explore more