Skip to main content
← Vulnerabilities

frr: ospf6d fails to enforce all OSPFv3 packets use IPv6 link-local addresses

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.1MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

9Pcve.now Index 9 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.1/10CVSS 6.1
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

CVE-2026-119776 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.1 (medium) and affects frrouting; a fix or patch is referenced.

Published
Last modified
Published
Not listed in CISA KEV
9/100 · provisional
Fix
Fix or patch referenced
None on Exploit-DB, Metasploit or GitHub

Summary

The FRRouting routing software's OSPFv3 implementation for IPv6 fails to check that incoming packets use a link-local source address and a link-local or protocol multicast destination. An attacker on the network, who needs low-privilege access, can use this to form OSPFv3 adjacencies from unexpectedly distant IPv6 hosts.

Read the original description

In all prior released versions of FRRouting, the OSPFv3 (for IPv6) implementation does not check that OSPFv3 packets have a link-local source address and either a link-local destination or one of the protocol multicast destination groups. This may enable malicious actors to establish OSPFv3 adjacencies from unexpectedly, distant IPv6 hosts. Proper usage of OSPFv3 authentication trailers (RFC 7166, as is best practice) prevents full exploitation of this issue, though may allow a malicious actor to waste CPU on authentication checks. Note the linked PR #23935 is not sufficient to fix the issue as it only verifies the source address. It is the destination address that must be checked. Required configuration: The OSPFv3 for IPv6 routing protocol must be running (ospf6d process) and in use (enabled globally with "router ospf6" and on specific interfaces with "ipv6 ospf6 area".) Workaround: either: • configure OSPFv3 authentication trailers ("ipv6 ospf6 authentication") • or ensure through firewall configuration that only packets with link-local or multicast destination addresses are accepted on input for IPv6 protocol 89 (OSPF). Note that checking the source address is insufficient, as some routers may (unexpectedly) forward packets with global-scoped IPv6 destination addresses even if they have link-local source addresses.

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • frrouting frrouting

    All versions

Evidence 2

  1. Patch
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-119776

Is CVE-2026-119776 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119776?

frrouting: all versions.Source: cve.now feed data