Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

Arbitrary Code Execution in shiba

CVE-2020-7738GHSA-jvf4-g24p-2qgw

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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

  • npm shiba

    Affected
    <= 1.2.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS
  • CVE-2020-7738: 1.55% estimated exploitation activity in the next 30 days; percentile 75.14 (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.

All versions of package shiba are vulnerable to Arbitrary Code Execution due to the default usage of the function load() of the package js-yaml instead of its secure replacement , safeLoad().

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

    Amended from ghsa record GHSA-jvf4-g24p-2qgw

  2. Revision 1 · created ·

    Published from osv record GHSA-jvf4-g24p-2qgw

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-2020-7738

Advisory: Arbitrary Code Execution in shiba
IDs: CVE-2020-7738, GHSA-jvf4-g24p-2qgw
Record: https://patchnext.com/advisories/cve-2020-7738 (revision 2, source checked 26 Oct 2026, 12:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm shiba: affected <= 1.2.1

## Suggested inspection (read-only)
- `npm ls shiba --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on shiba.
- 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://osv.dev/vulnerability/GHSA-jvf4-g24p-2qgw (OSV record GHSA-jvf4-g24p-2qgw lists affected ranges: npm shiba >=0 <=1.2.1)
- Verified: https://github.com/advisories/GHSA-jvf4-g24p-2qgw (GitHub-reviewed advisory GHSA-jvf4-g24p-2qgw lists affected ranges: npm shiba >=0 <=1.2.1)

Commands are suggestions: review each one before running it.

Loading voting…