dbcve.org
ShcApplication · Neurobin

CVE-2025-9176

HIGH · 7.8 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to after 4.0.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in neurobin shc up to 4.0.3. Impacted is the function make of the file src/shc.c of the component Environment Variable Handler. The manipulation results in os command injection. The attack is only possible with local access. The exploit has been released to the public and may be exploited.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability exists in neurobin shc up to version 4.0.3 in the make function within src/shc.c's Environment Variable Handler. The vulnerability allows local attackers to execute arbitrary OS commands through unsanitized environment variable manipulation.

MitigationUpgrade neurobin shc to a version beyond 4.0.3 that addresses the command injection in the environment variable handler, or implement input validation/sanitization for all environment variables before they are used in command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShcApplication
Affected:<= 4.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if neurobin shc is installed
    Run 'which shc' or 'shc -V' on Linux/Unix systems. On Debian-based systems, run 'dpkg -l | grep shc'. On RHEL-based systems, run 'rpm -qa | grep shc'.
    Affected if shc is found installed on the system
  2. Identify the installed shc version
    Run 'shc -V' or 'shc --version' to display the version number. Compare this against the affected range: version 4.0.3 or lower.
    Affected if The version displayed is 4.0.3 or any version lower than 4.0.3
  3. Verify if scripts are compiled using shc
    Search for shc usage in build scripts, Makefiles, or deployment pipelines: grep -r 'shc' /path/to/build/files. Check for commands like 'shc -f script.sh' or similar compilation invocations.
    Affected if shc is being used to compile shell scripts in the environment
  4. Check if environment variables can influence the shc compilation process
    Review the shc compilation command and environment. Look for any environment variables passed during the build (env | grep -i shc or review the build script). The vulnerability exploits unsanitized environment variables passed to the make function.
    Affected if Environment variables are passed to shc during script compilation without sanitization

You are affected if neurobin shc version 4.0.3 or lower is installed and is being used to compile shell scripts with uncontrolled environment variables reaching the compilation process.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.0.3
Interim mitigation

Upgrade neurobin shc to a version beyond 4.0.3 that addresses the command injection in the environment variable handler, or implement input validation/sanitization for all environment variables before they are used in command execution.

Recommended fix Moderate confidence

shc version 4.0.4 or later

  1. 1. Identify the current installed version of shc by running: shc -V or shc --version
  2. 2. Check if the installed version is 4.0.3 or earlier
  3. 3. Download the latest stable release of shc from the official GitHub repository: https://github.com/neurobin/shc
  4. 4. Extract the downloaded archive and navigate to the source directory
  5. 5. Remove the old installation: sudo make uninstall or manually delete the shc binary
  6. 6. Compile and install the new version: ./configure && make && sudo make install
  7. 7. Verify the new version is installed: shc -V
  8. 8. Ensure the new version is 4.0.4 or later, which contains the fix for CVE-2025-9176
Caveat Compile from source; ensure build dependencies (gcc, make, libssl-dev) are available. Review any changes in command-line options if migrating from very old versions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9176 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9176 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data