How severe is CVE-2019-11841?

CVE-2019-11841 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-11841?

CVE-2019-11841 affects the following packages: golang.org/x/crypto (Go). Ecosystems affected: Go.

How do I fix CVE-2019-11841?

Update golang.org/x/crypto to 0.0.0-20190424203555-c05e17bb3b2d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11841 is resolved across your whole dependency graph.

How do I detect CVE-2019-11841 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-11841 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-11841 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2019-11841, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-11841?

CVE-2019-11841 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-11841?

CVE-2019-11841 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-11841 published, and has it been updated?

CVE-2019-11841 was published on May 22, 2019 and was last updated on March 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2019-11841 — x/crypto

MEDIUMFix: golang/crypto@c05e17b

CVE-2019-11841 is a medium-severity (CVSS 5.9) CWE-347 vulnerability in golang.org/x/crypto. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for golang.org/x/crypto — see the affected versions and patch details below.

Golang/x/crypto message forgery vulnerability

Also known asGHSA-x3jr-pf6g-c48fGO-2023-1992

Published

May 22, 2019

Updated

Mar 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹golang.org/x/crypto

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/crypto`	all versions	0.0.0-20190424203555-c05e17bb3b2d`go get golang.org/x/crypto@v0.0.0-20190424203555-c05e17bb3b2d`

Affected Products

2 products · 3 configurations

debian linuxdebian

2 versions

8.09.0

Application

cryptogolang

1 version

2019-03-25

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A message-forgery issue was discovered in crypto/openpgp/clearsign/clear…

sec-consult.comNVDJul 2021

Report on packetstormsecurity.com

packetstormsecurity.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update golang.org/x/crypto to 0.0.0-20190424203555-c05e17bb3b2d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11841 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-11841 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works