How severe is CVE-2022-29526?

CVE-2022-29526 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-29526?

CVE-2022-29526 affects the following packages: golang.org/x/sys (Go). Ecosystems affected: Go.

How do I fix CVE-2022-29526?

Update golang.org/x/sys to 0.0.0-20220412211240-33da011f77ad or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29526 is resolved across your whole dependency graph.

How do I detect CVE-2022-29526 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-29526 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2022-29526 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-29526, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-29526?

CVE-2022-29526 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-29526?

CVE-2022-29526 is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-29526 published, and has it been updated?

CVE-2022-29526 was published on June 22, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2022-29526 — x/sys

MEDIUM

CVE-2022-29526 is a medium-severity (CVSS 5.3) Improper Privilege Management vulnerability in golang.org/x/sys. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for golang.org/x/sys — see the affected versions and patch details below.

golang.org/x/sys/unix has Incorrect privilege reporting in syscall

Also known asBIT-golang-2022-29526GHSA-p782-xgp4-8hr8GO-2022-0493

Published

Jun 22, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹golang.org/x/sys

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Reporting in syscall. When called with a non-zero flags parameter, the Faccessat function could incorrectly report that a file is accessible.

Specific Go Packages Affected

golang.org/x/sys/unix

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/sys`	all versions	0.0.0-20220412211240-33da011f77ad`go get golang.org/x/sys@v0.0.0-20220412211240-33da011f77ad`

Affected Products

3 products · 5 configurations

fedorafedoraproject

2 versions

3536

Application

gogolang

≥ 1.18.0 && < 1.18.2

range

Application

beegfs csi drivernetapp

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Assig…

github.comNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update golang.org/x/sys to 0.0.0-20220412211240-33da011f77ad or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29526 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OpenShift Service Mesh 2.1	`servicemesh-operator-0:2.1.5-1.el8`	RHSA-2022:6277
OSSO-1.0-RHEL-8	`openshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8:v1.0-28`	RHSA-2022:5699
Red Hat Ceph Storage 6.1	`rhceph/rhceph-6-dashboard-rhel9:6-75`	RHSA-2023:3642
Red Hat Enterprise Linux 8	`go-toolset:rhel8-8060020220527144311.97d7f71f`	RHSA-2022:5337
Red Hat Enterprise Linux 9	`golang-0:1.17.12-1.el9_0`	RHSA-2022:5799
Red Hat Migration Toolkit for Containers 1.7	`rhmtc/openshift-migration-must-gather-rhel8:v1.7.3-4`	RHSA-2022:5840
Red Hat OpenShift Container Platform 4.10	`atomic-openshift-service-idler-0:4.10.0-202207192015.p0.g39cfc66.assembly.stream.el8`	RHSA-2022:5729
Red Hat OpenShift Container Platform 4.11	`openshift4/cnf-tests-rhel8:v4.11.0-51`	RHBA-2022:5869

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-29526 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works