Vulnerability in sh (CVE-2026-54552)
Summary
Vulnerability in sh (CVE-2026-54552). Confidential information can be exposed externally. Exploitable via _uid. Mitigation: upgrade to 2.2.4 or later.
Original description
The description as published by the source.
Impact
The _uid option performed an incomplete privilege drop on Linux/Unix-like systems.
When sh was run from a process with elevated privileges, such as root, and a command was launched with _uid=, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.
This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on _uid as a privilege boundary when launching commands from a privileged parent process.
Patches
Upgrade to version >= 2.2.4
Workarounds
Avoid using _uid when the user represents a less-privileged user.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54552 has been found in sh.
Attackers can target a specific entry point like _uid over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.9/10.
What to do: upgrade sh to 2.2.4 or later.
If unsure, ask your IT team or search "sh CVE-2026-54552" on the vendor's site.
CVE-2026-54552 (sh) — CWE-273 / CVSS v3 7.9
Attack vector: local / no user interaction
Attack surface: _uid
Patched: 2.2.4 — apply immediately
Workaround: Avoid using _uid when the user represents a less-privileged user.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-273) exists in sh. Attackers reach the vulnerable code path via _uid.
Check the vendor advisory for the affected versions of sh. Attack surface: _uid.
Severity: High (CVSS 7.9/10). Confidential information can be exposed externally.
Update to 2.2.4.
Workaround: Avoid using _uid when the user represents a less-privileged user.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
shを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Avoid using `_uid` when the user represents a less-privileged user.パッチが適用されるまでの応急処置として、Avoid using
_uidwhen the user represents a less-privileged user. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade sh to 2.2.4ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com