Skip to main content
No exploitation reported

CVE-2018-12556

No exploitation reported by the sources we read.

  • Published2019-05-16
  • WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The signature verification routine in install.sh in yarnpkg/website through 2018-06-05 only verifies that the yarn release is signed by any (arbitrary) key in the local keyring of the user, and does not pin the signature to the yarn release key, which allows remote attackers to sign tampered yarn release packages with their own key.

Timeline

dates in UTC
  1. 2019-05-1617:29CVE publishedNVD

Versions per branch

NVD
Yarnpkg website
BranchAffectedFixed in
2018.x≤ 2018-06-05no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • node-yarnpkgUbuntu:26.10all versions · no fixed version listed
  • node-yarnpkgUbuntu:26.04:LTSall versions · no fixed version listed
  • node-yarnpkgUbuntu:25.10all versions · no fixed version listed
  • node-yarnpkgUbuntu:24.04:LTSall versions · no fixed version listed
  • node-yarnpkgUbuntu:22.04:LTSall versions · no fixed version listed
  • node-yarnpkgUbuntu:20.04:LTSall versions · no fixed version listed

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2019-05-16
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-8mxx-g9vw-r875

Frequently asked questions

What is CVE-2018-12556?

The signature verification routine in install.sh in yarnpkg/website through 2018-06-05 only verifies that the yarn release is signed by any (arbitrary) key in the local keyring of the user, and does not pin the signature to the yarn release key, which allows remote attackers to sign tampered yarn release packages with their own key.

Is CVE-2018-12556 actively exploited?

Active exploitation of CVE-2018-12556 has not been confirmed. Its EPSS score was 1.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-12556?

CVE-2018-12556 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running node-yarnpkg? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record