# CVE-2022-41906: OpenSearch Notifications is vulnerable to Server-Side Request Forgery (SSRF)

> Privileged users can exploit SSRF in the OpenSearch Notifications plugin to enumerate services or interact with internal resources via HTTP requests.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-pfc4-3436-jgrw

## What is CVE-2022-41906?

CVE-2022-41906 is a high-severity server-side request forgery vulnerability in opensearch-project notifications, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-41906?

It affects 1 product.


Products: Amazon Opensearch Notifications.

## How do I fix CVE-2022-41906?

No fix has been published for CVE-2022-41906 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41906 being exploited?

There is no known exploitation of CVE-2022-41906 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41906 and fix it if it is affected.

What it is: CVE-2022-41906 is a high-severity server-side request forgery vulnerability in opensearch-project notifications, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41906 in the wild and no public exploit code.

Affected product: opensearch-project notifications. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41906/ (Markdown: https://insights.sbomify.com/CVE-2022-41906/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41906
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41906
- OSV: https://osv.dev/vulnerability/CVE-2022-41906

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41906/
Summaries are generated and may contain mistakes; the official description above is the record.