CVE-2025-15099VulnerabilityPublished 26 Dec 2025

CVE-2025-15099: simstudioai sim · Improper Authentication

Affects simstudioai simSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubsimstudioai/sim`pkg:github/simstudioai/sim`Other threats	Affected =0.5.0 =0.5.1 =0.5.2 =0.5.3 =0.5.4 =0.5.5 =0.5.6 =0.5.7 =0.5.8 =0.5.9 =0.5.10 =0.5.11 =0.5.12 =0.5.13 =0.5.14 =0.5.15 =0.5.16 =0.5.17 =0.5.18 =0.5.19 =0.5.20 =0.5.21 =0.5.22 =0.5.23 =0.5.24 =0.5.25 =0.5.26 =0.5.27	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately apply the vendor-provided patch identified by commit e359dc2946b12ed5e45a0ec9c95ecf91bd18502a to all affected simstudioai sim instances running versions up to 0.5.27. 2. Restrict network access to internal APIs and the CRON Secret Handler component by implementing strict firewall rules and network segmentation to limit exposure. 3. Rotate and securely manage any secrets or API keys related to INTERNAL_API_SECRET to prevent reuse of compromised credentials. 4. Implement robust monitoring and logging of authentication attempts and API access to detect anomalous or unauthorized activities promptly. 5. Conduct regular security assessments and code reviews focusing on authentication mechanisms within simstudioai sim deployments. 6. Educate development and operations teams about the risks of improper secret handling and enforce secure coding practices. 7. If possible, deploy Web Application Firewalls (WAFs) or API gateways with anomaly detection to block suspicious requests targeting internal APIs. 8. Maintain an incident response plan tailored to vulnerabilities in AI simulation platforms to enable rapid containment and remediation.

Description

A vulnerability was identified in simstudioai sim up to 0.5.27. This vulnerability affects unknown code of the file apps/sim/lib/auth/internal.ts of the component CRON Secret Handler. The manipulation of the argument INTERNAL_API_SECRET leads to improper authentication. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The identifier of the patch is e359dc2946b12ed5e45a0ec9c95ecf91bd18502a. Applying a patch is the recommended action to fix this issue.

Impact

For European organizations, this vulnerability poses a risk of unauthorized remote access to internal APIs within simstudioai sim deployments. This can lead to unauthorized data disclosure, modification, or disruption of services relying on the sim platform. Organizations in sectors such as AI research, software development, telecommunications, and critical infrastructure that utilize simstudioai sim could face operational impacts or data breaches. The lack of required privileges or user interaction lowers the barrier for attackers, increasing the likelihood of exploitation if unpatched. While the direct impact on confidentiality, integrity, and availability is rated low individually, combined effects could allow attackers to pivot within networks or compromise sensitive internal functions. This could undermine trust in AI simulation environments and cause compliance issues under European data protection regulations such as GDPR if personal or sensitive data is involved. The availability of public exploit code further elevates the threat level, necessitating urgent patching and monitoring. Failure to address this vulnerability could result in reputational damage and financial losses for affected organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 04:30 UTC

Technical details

References

Community reviews

Related threats