# CVE-2024-41778: IBM Controller information disclosure

> Weak default password requirements in IBM Controller allow attackers to compromise user accounts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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:** 1 Mar 2025
- **Updated:** 1 Sep 2025
- **Also known as:** GHSA-f86r-6rph-2h3c

## What is CVE-2024-41778?

CVE-2024-41778 is a medium-severity vulnerability in IBM Controller, published on 1 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Controller 11.0.0 through 11.0.1 and 11.1.0 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2024-41778?

It affects 1 product.


Products: Ibm Controller.

## How do I fix CVE-2024-41778?

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

## Is CVE-2024-41778 being exploited?

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

## Other vulnerabilities in IBM Controller

- [CVE-2026-5065](https://insights.sbomify.com/CVE-2026-5065/): IBM Controller is affected by vulnerabilities (high 8.8)
- [CVE-2025-36017](https://insights.sbomify.com/CVE-2025-36017/): IBM Controller Information Disclosure (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41778 and fix it if it is affected.

What it is: CVE-2024-41778 is a medium-severity vulnerability in IBM Controller, published on 1 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41778 in the wild and no public exploit code.

Affected product: IBM Controller. 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-2024-41778/ (Markdown: https://insights.sbomify.com/CVE-2024-41778/index.md)
```

## Sources

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

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