# CVE-2025-66391: Missing authorization in n/a

> Read-only users can trigger password reset workflows, sending OTPs to attacker-controlled emails, enabling potential account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-gpmq-7782-jmhq

## What is CVE-2025-66391?

CVE-2025-66391 is a high-severity missing authorization vulnerability in n/a, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Citrix Cloud through 2025-11-10, an account with read-only access can trigger the beginning of a workflow for write operations, e.g., the system will send a one-time password to an attacker-controlled email address when the attacker attempts to reset the password of a user account.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-66391?


## How do I fix CVE-2025-66391?

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

## Is CVE-2025-66391 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66391 exists.

Public exploit code:

- https://github.com/mandeepsohal/CVE-2025-66391 (github_poc): https://github.com/mandeepsohal/CVE-2025-66391

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66391 and fix it if it is affected.

What it is: CVE-2025-66391 is a high-severity missing authorization vulnerability in n/a, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66391 exists.

Affected product: n/a. 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-2025-66391/ (Markdown: https://insights.sbomify.com/CVE-2025-66391/index.md)
```

## Sources

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

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