# CVE-2025-36076: IBM Cognos Analytics versions 12.0.4 and 12.1.3 is affected by security vulnerabilities

> Authenticated users can access sensitive information stored in source code, potentially aiding further attacks against IBM Cognos Analytics.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-qv83-qj3c-qc9v

## What is CVE-2025-36076?

CVE-2025-36076 is a medium-severity vulnerability in IBM Cognos Analytics, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Cognos Analytics 12.1.0 through 12.1.3 FP1, and 12.0.4 through 12.0.4 FP2 stores sensitive information in source code could be used by an authenticated user in further attacks against the system.

Weakness: CWE-540 (Inclusion of Sensitive Information in Source Code)

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


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

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

## Is CVE-2025-36076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-36076 is a medium-severity vulnerability in IBM Cognos Analytics, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36076 in the wild and no public exploit code.

Affected product: IBM Cognos Analytics. 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-36076/ (Markdown: https://insights.sbomify.com/CVE-2025-36076/index.md)
```

## Sources

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

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