Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

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

CVE-2022-29526GHSA-p782-xgp4-8hr8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (golang.org/x/sys 0.0.0-20220412211240-33da011f77ad), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go golang.org/x/sys

    Affected
    < 0.0.0-20220412211240-33da011f77ad
    Fixed in
    0.0.0-20220412211240-33da011f77ad

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2022-29526: 2.95% estimated exploitation activity in the next 30 days; percentile 87.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-p782-xgp4-8hr8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-29526

Advisory: golang.org/x/sys/unix has Incorrect privilege reporting in syscall
IDs: CVE-2022-29526, GHSA-p782-xgp4-8hr8
Record: https://patchnext.com/advisories/cve-2022-29526 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: golang.org/x/sys 0.0.0-20220412211240-33da011f77ad. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go golang.org/x/sys: affected < 0.0.0-20220412211240-33da011f77ad; fixed in 0.0.0-20220412211240-33da011f77ad

## Suggested inspection (read-only)
- Go golang.org/x/sys: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on golang.org/x/sys.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p782-xgp4-8hr8 (GitHub-reviewed advisory GHSA-p782-xgp4-8hr8 lists affected ranges: Go golang.org/x/sys >=0 <0.0.0-20220412211240-33da011f77ad)

Commands are suggestions: review each one before running it.

Loading voting…