PatchTheCVECVE-2022-1117: A vulnerability was found in fapolicyd
CVE-2022-1117 is a high-severity flaw (CVSS 8.4) affecting fapolicyd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A vulnerability was found in fapolicyd. The vulnerability occurs due to an assumption on how glibc names the runtime linker, a build time regular expression may not correctly detect the runtime linker. The consequence is that the pattern detection for applications launched by the run time linker may fail to detect the pattern and allow execution.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.4 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 74%) |
| CISA exploited list | No |
| Weakness | CWE-552 |
| Published | 2022-08-29 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-1117?
fapolicyd: upgrade to 1.1.2. Exact commands for each OS are on this page.
Is CVE-2022-1117 being exploited?
CVE-2022-1117 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-1117 affect?
CVE-2022-1117 affects fapolicyd. Severity is high (CVSS 8.4). A vulnerability was found in fapolicyd. The vulnerability occurs due to an assumption on how glibc names the runtime linker, a build time regular expression may not correctly detect the runtime linker. The consequence is that the pattern de
How urgent is CVE-2022-1117?
Priority 36/100. High severity