CVE-2026-13510
Deferred Deferred - Pending Action

Weak Hash in SimStudioAI SIM Application

Vulnerability report for CVE-2026-13510, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-28

Last updated on: 2026-06-29

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-28
Last Modified
2026-06-29
Generated
2026-07-19
AI Q&A
2026-06-29
EPSS Evaluated
2026-07-17
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
simstudioai sim to 0.6.92 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-328 The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).
CWE-327 The product uses a broken or risky cryptographic algorithm or protocol.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in SimStudioAI sim up to version 0.6.92, specifically in an unknown functionality within the Password Protection Handler component located in the library apps/sim/lib/core/security/deployment.ts. The issue involves the use of a weak hash due to manipulation, which can be exploited remotely. Although the attack complexity is high and exploitation is difficult, the exploit has been made public. A fix has been proposed but is not yet accepted.

Detection Guidance

This vulnerability involves the forgery of unsigned base64 authentication tokens used in SimStudioAI Sim deployments. Detection can focus on monitoring for unusual authentication token patterns, especially tokens containing truncated SHA-256 hashes of passwords that are only 8 characters long and lack server-side signatures or HMAC.

To detect potential exploitation attempts, you can monitor logs for repeated failed authentication attempts or brute-force token guessing activities targeting deployment endpoints.

Specific commands are not provided in the resources, but general approaches include:

  • Inspect HTTP request headers or cookies for base64 tokens matching the vulnerable pattern.
  • Use network traffic analysis tools (e.g., tcpdump, Wireshark) to capture and analyze tokens sent to deployment endpoints.
  • Search server logs for repeated authentication failures or suspicious token usage.
  • Implement rate limiting and monitoring on authentication endpoints to detect brute-force attempts.
Impact Analysis

The vulnerability allows an attacker to remotely exploit the use of a weak hash in the password protection mechanism. This could potentially weaken the security of password handling, making it easier for attackers to compromise password-related data or authentication processes. However, the attack complexity is high and exploitation is difficult, which may limit the likelihood of successful attacks.

Compliance Impact

The vulnerability involves the use of a weak hash in the Password Protection Handler component, which could potentially weaken the security of password protection mechanisms.

Weak password hashing can lead to increased risk of unauthorized access or data breaches, which may impact compliance with standards and regulations such as GDPR and HIPAA that require adequate protection of personal and sensitive data.

However, the provided information does not explicitly state the direct impact on compliance with these regulations.

Mitigation Strategies

Immediate mitigation steps include:

  • Apply the fix from the pending pull request that replaces unsigned base64 tokens with HMAC-signed tokens bound to the full SHA-256 hash of the encrypted password.
  • Remove the use of truncated password hashes in client-controlled tokens to prevent token forgery.
  • Implement rate limiting and monitoring on authentication endpoints to reduce the risk of brute-force token guessing.
  • Be aware that the current fix has a flaw accepting tokens with future timestamps, so additional validation on token timestamps should be enforced if possible.
  • Until the fix is fully accepted and deployed, consider restricting remote access to the affected deployment endpoints to trusted networks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-13510. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart