CRITICAL CVSS 9.8
Published: 2025-08-11

CVE-2025-8660

broadcom symantec_pgp_encryption Security Advisory (CVE-2025-8660)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-8660?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-8660 impacting broadcom symantec_pgp_encryption. Evaluated with CVSS Base Score of 9.8 (CRITICAL).

Original NVD Description

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

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product broadcom / symantec_pgp_encryption
Affected Versions 11.0.1
Weakness Enumeration CWE-269

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-8660 impacting broadcom symantec_pgp_encryption.

⚡ Nuclei Detection Template (YAML) cve-2025-8660.yaml
id: cve-2025-8660

info:
  name: broadcom symantec_pgp_encryption - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2025-8660 affecting broadcom symantec_pgp_encryption.
    Evaluation: Privilege escalation occurs when a user gets access to more resources or functionality than they are normally allowed....
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-8660
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2025-8660
    cwe-id: CWE-269
  tags: cve,cve-2025-8660,broadcom,symantec_pgp_encryption,critical

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "symantec_pgp_encryption"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-8660.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-8660
# Target: broadcom symantec_pgp_encryption | CVSS: 9.8 (CRITICAL)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-8660 (broadcom symantec_pgp_encryption)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against broadcom symantec_pgp_encryption scope (11.0.1).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-8660.sh
# Recommended Remediation & Patching Commands for CVE-2025-8660
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install symantec_pgp_encryption 2>/dev/null || \
sudo dnf upgrade symantec_pgp_encryption 2>/dev/null || \
sudo yum update symantec_pgp_encryption

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i symantec_pgp_encryption 2>/dev/null || rpm -qa | grep -i symantec_pgp_encryption

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-8660 in broadcom symantec_pgp_encryption?

Review vendor-specific security notices and update broadcom symantec_pgp_encryption packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-8660?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-8660?

CVE-2025-8660 is classified with a CVSS 3.1 Base Score of 9.8 (CRITICAL). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
9.8
CRITICAL SEVERITY
CVE ID CVE-2025-8660
Weakness CWE-269
Vendor broadcom
Product symantec_pgp_encryption
Published 2025-08-11
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H