CVE-2026-119776

6.1 MEDIUM 0.4% exploit odds Fix listed Other Network gear

What it is

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.

At a glance

Exploitability: Can be exploited over the network with a low-privilege account. High risk of data tampering, service disruption.
Exploit odds: 0.4% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2026-10-30 16:14 UTC ReservedThe CVE id was reserved by its CNA
2026-11-04 15:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-11-04 17:17 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.4% in the next 30 days (EPSS).
Severity: 6.1 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2026-11-04 15:17 UTC
Last modified: 2026-11-04 17:17 UTC
Exploit probability: 0.4% · EPSS, next 30 days
Weakness: CWE-304
Record status: Received

Attack profile CVSS 4.0 · 6.1

Attack vector: Network
Complexity: Low
Attack requirements: Present
Privileges needed: Low
User interaction: None
Confidentiality: Low
Integrity: High
Availability: High

Raw vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:X

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-119776.md and follow it. Check whether this project is affected by CVE-2026-119776. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record