CVE-2022-1650 is a high-severity (CVSS 8.1) CWE-212 vulnerability in eventsource. 1 public exploit reference exists, so weaponization risk is real. A fix is available for eventsource — see the affected versions and patch details below.
Improper Removal of Sensitive Information Before Storage or Transfer in eventsource/eventsource
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-1650 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
eventsourcenpmDescription
Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository eventsource/eventsource prior to v2.0.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | eventsource | all versions | 1.1.1npm install eventsource@1.1.1 |
| 📦npm | eventsource | ≥ 2.0.0&&< 2.0.2 | 2.0.2npm install eventsource@2.0.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eventsource, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update eventsource to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1650 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-1650 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-1650. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| .NET Core on Red Hat Enterprise Linux | rh-dotnet31-dotnet-0:3.1.422-1.el7_9 | RHSA-2022:6037 |
| .NET Core on Red Hat Enterprise Linux | rh-dotnet60-dotnet-0:6.0.107-1.el7_9 | RHBA-2022:5721 |
| OpenShift Service Mesh 2.1 | openshift-service-mesh/kiali-rhel8:1.36.10-2 | RHSA-2022:5006 |
| Red Hat Ceph Storage 6.1 | rhceph/rhceph-6-dashboard-rhel9:6-75 | RHSA-2023:3642 |
| Red Hat Enterprise Linux 8 | dotnet6.0-0:6.0.107-1.el8_6 | RHBA-2022:5747 |
| Red Hat Enterprise Linux 8 | dotnet3.1-0:3.1.422-1.el8_6 | RHSA-2022:6057 |
| Red Hat Enterprise Linux 9 | dotnet6.0-0:6.0.107-1.el9_0 | RHBA-2022:5749 |
| Red Hat Fuse Online 7.10.2.P1 | eventsource | RHSA-2022:5030 |
Frequently Asked Questions
Is CVE-2022-1650 in your dependencies?
O3 Security finds CVE-2022-1650 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.