CVE-2026-37457: An off-by-one out-of-bounds write vulnerability in the bgp_flowspec_op_decode() function (bgpd/bgp_flowspec...
An off-by-one out-of-bounds write vulnerability in the bgp_flowspec_op_decode() function (bgpd/bgp_flowspec_util.c) of FRRouting (FRR) stable/10.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted FlowSpec component.
Security readout for executives and security teams
Plain-English summary
This flaw can crash or disrupt FRRouting BGP services when they process a specially crafted FlowSpec component. For organizations relying on FRR for routing, the business impact is availability loss, not data theft. The bundle does not show active exploitation.
Executive priority
Prioritize patching where FRR supports production routing or has exposed BGP peers. The issue is availability-focused, but routing outages can create broad business disruption.
Technical view
CVE-2026-37457 is an off-by-one out-of-bounds write in FRR bgp_flowspec_op_decode() in bgpd/bgp_flowspec_util.c. The CVSS 3.1 vector is network-accessible, low-complexity, unauthenticated, no user interaction, with high availability impact only.
Likely exposure
Exposure is most likely where FRRouting stable/10.0 bgpd processes BGP FlowSpec components. The provided affected-product metadata is incomplete, so teams should verify packaged FRR versions through FRRouting and Red Hat advisory data.
Exploitation context
The source bundle rates this as remotely reachable DoS. CISA KEV is false, and no provided source states active exploitation. Treat internet-facing or untrusted-peer BGP FlowSpec processing as higher operational risk.
Researcher notes
The bundle identifies CWE-787 and the vulnerable function, but affected CPEs are listed as n/a. Avoid assuming broader version impact without vendor confirmation. No exploit details or active exploitation evidence are provided.
Mitigation direction
Apply FRRouting or distribution vendor updates covering CVE-2026-37457.
Review the linked Red Hat advisories for package-specific remediation.
Restrict BGP sessions to trusted peers where operationally possible.
Review FlowSpec acceptance policies and disable unnecessary exposure.
Monitor bgpd stability and crash alerts until remediation is complete.
Validation and detection
Inventory systems running FRRouting or vendor-packaged FRR bgpd.
Confirm deployed FRR versions against FRRouting and Red Hat advisory data.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.