In FRRouting FRR before 8.5, the service user (usually frr) can escalate its privileges to root by monitoring the configuration directory (/etc/frr) and replacing config files upon creation with, for example, symlinks to change the ownership of arbitrary files. This is a TOCTOU Race Condition caused by a combination of touch and chown.
CVE-2022-42917
Score 6.7 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 6.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.7
- EG Score
- 6.7(high)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity67% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 14, 2026
Advisory Details (4)
Auto-updated Sep 14, 2026Comparing frr-8.4...frr-8.5 · FRRouting/frr · GitHub
https://github.com/FRRouting/frr/compare/frr-8.4...frr-8.5commit 972cdc560e33 (FRRouting/frr)
Fix landed in FRRouting/frr commit 972cdc560e33 — awaiting tagged release
https://github.com/FRRouting/frr/commit/972cdc560e339d70c0ee5fb70ec636ab78f00bcaVendor Advisories for CVE-2022-42917(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 16:50 UTCEG score recompute
- 2026-09-19 16:50 UTCGHSA enrichment
- 2026-09-19 15:38 UTCEPSS rescore
- 2026-09-18 18:13 UTCGHSA enrichment
- 2026-09-17 19:35 UTCEG score recompute
- 2026-09-17 19:35 UTCGHSA enrichment
- 2026-09-16 17:58 UTCEG score recompute
- 2026-09-16 17:58 UTCGHSA enrichment
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-16 05:10 UTCEPSS rescore
- 2026-09-15 18:15 UTCEG score recompute
- 2026-09-15 18:15 UTCGHSA enrichment
- 2026-09-15 03:07 UTCEPSS rescore
- 2026-09-14 19:21 UTCEG score recompute
- 2026-09-14 19:21 UTCGHSA enrichment
- 2026-09-14 18:27 UTCEG score recompute
- 2026-09-14 18:27 UTCGHSA enrichment
- 2026-09-14 00:20 UTCEG score recompute▲ 6.70
- 2026-09-14 00:19 UTCNVD updateCVSS v3 → 6.7 · severity → MEDIUM
- 2026-09-13 23:30 UTCEG score recompute
- 2026-09-13 23:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2022-42917?
When was CVE-2022-42917 disclosed?
Is CVE-2022-42917 actively exploited?
What is the CVSS score of CVE-2022-42917?
How do I remediate CVE-2022-42917?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-42917
Is Your Infrastructure Affected by CVE-2022-42917?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.