# CVE-2025-8660: Privilege Escalation in Symantec PGP Encryption 11.0.1

> Attackers can escalate privileges in Symantec PGP Encryption to gain unauthorized access to additional system resources or functionality.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2025
- **Updated:** 11 Aug 2025
- **Also known as:** GHSA-7693-45r8-8v4h

## What is CVE-2025-8660?

CVE-2025-8660 is a medium-severity vulnerability in Broadcom Symantec PGP Encryption, published on 11 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Privilege escalation occurs when a user gets access to more resources or functionality than they are normally allowed.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Broadcom Symantec Pgp Encryption.

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

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

## Is CVE-2025-8660 being exploited?

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

## Other vulnerabilities in Broadcom Symantec PGP Encryption

- [CVE-2025-8661](https://insights.sbomify.com/CVE-2025-8661/): Stored Cross-Site Scripting in Symantec PGP Encryption 11.0.1 (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8660 is a medium-severity vulnerability in Broadcom Symantec PGP Encryption, published on 11 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-8660 in the wild and no public exploit code.

Affected product: Broadcom Symantec PGP Encryption. 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-8660/ (Markdown: https://insights.sbomify.com/CVE-2025-8660/index.md)
```

## Sources

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

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