Skip to main content
VulnerabilityPublished

CVE-2026-54552: amoffat sh · Improper Check for Dropped Privileges

Affects amoffat shSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.9 High : upgrade to 2.2.4 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.4
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade amoffat sh to 2.2.4.

Affected software

ProductAffectedFixed in
amoffatshAffected
  • <2.2.4
Fixed in
  • 2.2.4
PyPIshpkg:pypi/shOther threatsAffected
  • <2.2.4
Fixed in
  • 2.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to amoffat sh version 2.2.4 or later, where the privilege drop sequence correctly establishes the target user's UID, primary GID, and supplementary groups. No other mitigations are specified. Patch status is confirmed fixed in version 2.2.4.

Description

sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process's supplementary groups because the privilege-drop sequence does not fully establish the target user's UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.

References

Community reviews

Loading reviews…