# CVE-2026-84389: Open redirect in FortiSIEM

> An open redirect vulnerability in FortiSIEM allows attackers to redirect users to untrusted sites, potentially facilitating phishing or further attacks.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-3fm5-pxmf-24vc

## What is CVE-2026-84389?

CVE-2026-84389 is a low-severity vulnerability in Fortinet FortiSIEM, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A url redirection to untrusted site ('open redirect') vulnerability in Fortinet FortiSIEM 7.5.0 through 7.5.1, FortiSIEM 7.4.1 through 7.4.2 may allow attacker to execute unauthorized code or commands via <insert attack vector here>

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-84389?


## How do I fix CVE-2026-84389?

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

## Is CVE-2026-84389 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84389 and fix it if it is affected.

What it is: CVE-2026-84389 is a low-severity vulnerability in Fortinet FortiSIEM, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-84389 in the wild and no public exploit code.

Affected product: Fortinet FortiSIEM. 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-2026-84389/ (Markdown: https://insights.sbomify.com/CVE-2026-84389/index.md)
```

## Sources

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

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