# CVE-2026-13510: SimStudioAI sim Password Protection deployment.ts weak hash

> Attackers can bypass password protection in SimStudioAI sim due to the use of a weak hash algorithm in the deployment security handler.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-g2q4-cj5p-88qg

## What is CVE-2026-13510?

CVE-2026-13510 is a medium-severity vulnerability in SimStudioAI sim, published on 28 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

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

## Is CVE-2026-13510 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13510 is a medium-severity vulnerability in SimStudioAI sim, published on 28 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13510 exists.

Affected product: SimStudioAI sim. 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-13510/ (Markdown: https://insights.sbomify.com/CVE-2026-13510/index.md)
```

## Sources

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

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