# CVE-2024-54855: Hardcoded credentials in n/a

> Static SSH keys in Vanilla OS 2 Core image allow attackers to perform man-in-the-middle attacks during host connections.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-67pc-hqr2-g34h

## What is CVE-2024-54855?

CVE-2024-54855 is a medium-severity vulnerability in n/a, published on 13 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

fabricators Ltd Vanilla OS 2 Core image v1.1.0 was discovered to contain static keys for the SSH service, allowing attackers to possibly execute a man-in-the-middle attack during connections with other hosts.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Fabricators Vanilla Os Core Image.

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

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

## Is CVE-2024-54855 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54855 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54855 is a medium-severity vulnerability in n/a, published on 13 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54855 exists.

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

## Sources

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

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