CVE-2019-9153: Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed me

Q: How do I fix CVE-2019-9153?

openpgpjs: upgrade to newer than 4.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2019-9153 being exploited?

CVE-2019-9153 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-9153 affect?

CVE-2019-9153 affects openpgpjs. Severity is high (CVSS 7.5). Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed messages by replacing its signatures with a "standalone" or "timestamp" signature.

Q: How urgent is CVE-2019-9153?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2019-9153 is a high-severity flaw (CVSS 7.5) affecting openpgpjs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed messages by replacing its signatures with a "standalone" or "timestamp" signature.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Weakness	CWE-347
Published	2019-08-22
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: openpgpjs

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-08-22 16:15 UTCPublished CVE record published
2026-06-17 02:43 UTCUpdated Record last modified

openpgpjs openpgpjs UPGRADE

Affected: <= 4.1.2

Fixed in: newer than 4.1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy openpgpjs || rpm -q openpgpjs || openpgpjs --version

2. UPGRADE to newer than 4.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade openpgpjs

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade openpgpjs

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-9153?

openpgpjs: upgrade to newer than 4.1.2. Exact commands for each OS are on this page.

Is CVE-2019-9153 being exploited?

CVE-2019-9153 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-9153 affect?

CVE-2019-9153 affects openpgpjs. Severity is high (CVSS 7.5). Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed messages by replacing its signatures with a "standalone" or "timestamp" signature.

How urgent is CVE-2019-9153?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-9155 MEDIUM 5.9 UPGRADE A cryptographic issue in OpenPGP.js <=4.2.0 allows an attacker who is able provide forged messages and gain fe
CVE-2019-9154 HIGH 7.5 UPGRADE Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to pass off unsign
CVE-2015-8013 HIGH 7.5 UPGRADE s2k.js in OpenPGP.js will decrypt arbitrary messages regardless of passphrase for crafted PGP keys which allow

References

← Back to latest CVEs