CVE-2022-41906 json
OpenSearch Notifications is vulnerable to Server-Side Request Forgery (SSRF)
published 2022-11-11 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-45043
- cvss
- 7.7
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
OpenSearch Notifications is a notifications plugin for OpenSearch that enables other plugins to send notifications via Email, Slack, Amazon Chime, Custom web-hook etc channels. A potential SSRF issue in OpenSearch Notifications Plugin starting in 2.0.0 and prior to 2.2.1 could allow an existing privileged user to enumerate listening services or interact with configured resources via HTTP requests exceeding the Notification plugin's intended scope. OpenSearch 2.2.1+ contains the fix for this issue. There are currently no recommended workarounds.
Patch / fix
- amazon opensearch_notifications 2.2.1.0
- github.com/opensearch-project/notifications#496 pull request
- github.com/opensearch-project/notifications#507 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.7 | CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N |
Affected products
- opensearch-project notifications
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/opensearch-project/notifications/pull/496
patch, third-party-advisory
-
github.com
/opensearch-project/notifications/pull/507
patch, third-party-advisory
-
github.com
/opensearch-project/notifications/security/advisories/GHSA-pfc4-3436-jgrw
third-party-advisory
Sources
- CVE List CVE-2022-41906
- NVD CVE-2022-41906
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.