CVE-2023-41037

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenPGP.js is a JavaScript implementation of the OpenPGP protocol. In affected versions OpenPGP Cleartext Signed Messages are cryptographically signed messages where the signed text is readable without special tools. These messages typically contain a "Hash: ..." header declaring the hash algorithm used to compute the signature digest. OpenPGP.js up to v5.9.0 ignored any data preceding the "Hash: ..." texts when verifying the signature. As a result, malicious parties could add arbitrary text to a third-party Cleartext Signed Message, to lead the victim to believe that the arbitrary text was signed. A user or application is vulnerable to said attack vector if it verifies the CleartextMessage by only checking the returned verified property, discarding the associated data information, and instead _visually trusting_ the contents of the original message. Since verificationResult.data would always contain the actual signed data, users and apps that check this information are not vulnerable. Similarly, given a CleartextMessage object, retrieving the data using getText() or the text field returns only the contents that are considered when verifying the signature. Finally, re-armoring a CleartextMessage object (using armor() will also result in a "sanitised" version, with the extraneous text being removed. This issue has been addressed in version 5.10.1 (current stable version) which will reject messages when calling openpgp.readCleartextMessage() and in version 4.10.11 (legacy version) which will will reject messages when calling openpgp.cleartext.readArmored(). Users are advised to upgrade. Users unable to upgrade should check the contents of verificationResult.data to see what data was actually signed, rather than visually trusting the contents of the armored message.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 29, 2023

Last Modified

June 17, 2026

References (2)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
openpgp—
  • every version up to 4.10.11: fixed in 4.10.11
  • 5.0.0 up to 5.10.1: fixed in 5.10.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  5. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  7. 2026-10-18 07:53 UTCEG score recompute
  8. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-13 05:24 UTCOSV refresh
  14. 2026-10-12 18:20 UTCEG score recompute
  15. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-11 21:46 UTCEG score recompute
  17. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  21. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  25. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.4% · 26th percentile
Show 59 more
  1. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-09-30 16:29 UTCEG score recompute
  3. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  4. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  5. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  6. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  7. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  9. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  10. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-23 01:32 UTCOSV refresh
  12. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  26. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  27. 2026-09-03 20:16 UTCOSV refresh
  28. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  29. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  30. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  31. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  42. 2026-08-17 09:08 UTCOSV refresh
  43. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  49. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  53. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-08-02 03:41 UTCOSV refresh
  56. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-41037?
CVE-2023-41037 is a medium-severity vulnerability; its CVE record was published on August 29, 2023. OpenPGP.js is a JavaScript implementation of the OpenPGP protocol. In affected versions OpenPGP Cleartext Signed Messages are cryptographically signed messages where the signed text is readable without special tools. These messages typically contain a "Hash: ..." header declaring the hash algorithm…
When was the CVE record for CVE-2023-41037 published?
The CVE record for CVE-2023-41037 was published on August 29, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-41037 actively exploited?
CVE-2023-41037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-41037?
CVE-2023-41037 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2023-41037?
A fix for CVE-2023-41037 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-41037

Explore →

Is Your Infrastructure Affected by CVE-2023-41037?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs