# CVE-2025-12491: Senstar Symphony FetchStoredLicense Information Disclosure Vulnerability

> Remote attackers can exploit the FetchStoredLicense method to disclose stored credentials, potentially leading to further system compromise.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-gghq-p8vx-g4c3

## What is CVE-2025-12491?

CVE-2025-12491 is a high-severity vulnerability in Senstar Symphony, published on 23 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Senstar Symphony FetchStoredLicense Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Senstar Symphony. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the implementation of FetchStoredLicense method. The issue results from the exposure of sensitive information. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-26908.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-12491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12491 is a high-severity vulnerability in Senstar Symphony, published on 23 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12491 in the wild and no public exploit code.

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

## Sources

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

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