# CVE-2026-101034: Security Advisory for offline recovery of Symantec GSS 3.3 RU11 stored domain credentials


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:P/S:P/AU:Y/R:U/V:D/RE:H/U:Amber`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-wm2j-33wx-q4cw

## What is CVE-2026-101034?

CVE-2026-101034 is a medium-severity vulnerability in Broadcom Symantec Ghost Solution Suite, published on 27 Oct 2026. 

### Official description

An attacker who obtained the hardcoded key could decrypt domain/service account passwords, task run-as credentials, and sysprep passwords stored in or transmitted by GSS Deployment Server installation.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-101034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101034 is a medium-severity vulnerability in Broadcom Symantec Ghost Solution Suite, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101034 in the wild and no public exploit code.

Affected product: Broadcom Symantec Ghost Solution Suite. 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-101034/ (Markdown: https://insights.sbomify.com/CVE-2026-101034/index.md)
```

## Sources

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

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