Secuno
ENNL
Book demo

CVE-2022-1650

Eventsource vulnerability

8.1 HIGHPublic exploitEPSS 1.86%
  1. Published12 May 2022

Description

Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository eventsource/eventsource prior to v2.0.2.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

Eventsource≥ 2.0.0 < 2.0.2 · < 1.1.1
Debian Linux10.0

Remediation

Fixed in
Eventsource≥ 2.0.2

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-850948.8
The Canva Android App before 2.376.0 did not restrict the headers returned to an…
CVE-2026-428809.6
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From versions…
CVE-2024-433848.0
A low privileged remote attacker can gain the root password due to improper removal of…
CVE-2026-328919.0
Anchorr is a Discord bot for requesting movies and TV shows and receiving notifications…
CVE-2022-28189.8
Improper Removal of Sensitive Information Before Storage or Transfer in GitHub…
CVE-2022-03558.8
Improper Removal of Sensitive Information Before Storage or Transfer in NPM simple-get…

Frequently asked

Is CVE-2022-1650 being actively exploited?

CVE-2022-1650 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.86%.

How severe is CVE-2022-1650?

CVE-2022-1650 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 1.86% probability of exploitation.

Which products are affected by CVE-2022-1650?

Affected products include Eventsource, Debian Linux.

How do I fix CVE-2022-1650?

Upgrade affected software to a fixed version, for example Eventsource 2.0.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2022-1650 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.