CVE-2025-53636VulnerabilityPublished 11 Jul 2025Updated 14 Jul 2025

CVE-2025-53636: OSC ondemand · Uncontrolled Resource Consumption

Affects OSC ondemandSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 4.0.6 or 3.1.14 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.6, 3.1.14

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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 on the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Jul 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 26 Oct 2026.

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

Upgrade osc/ondemand to 4.0.6 or 3.1.14.

Affected software

Product	Affected	Fixed in
GitHubosc/ondemand`pkg:github/osc/ondemand`Other threats	Affected <3.1.14 <4.0.6	Fixed in 3.1.14 4.0.6

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

AI-suggested

European organizations should immediately verify their ondemand version and upgrade to 3.1.14 or 4.0.6 or later to apply the official patch. Until patched, administrators should implement strict user activity monitoring and limit the ability of users to generate excessive errors in the shell app. Implementing quota controls on log file sizes and disk usage can help prevent resource exhaustion. Additionally, configuring log rotation policies with aggressive rotation and compression can mitigate log file growth. Restricting shell app access to trusted users and enforcing least privilege principles reduces the risk of exploitation. Network-level controls such as rate limiting and anomaly detection can identify and block attempts to flood logs. Regular auditing of log files and system resource usage will help detect early signs of exploitation. Finally, organizations should prepare incident response plans to quickly recover from potential DoS events caused by this vulnerability.

Description

Open OnDemand is an open-source HPC portal. Users can flood logs by interacting with the shell app and generating many errors. Users who flood logs can create very large log files causing a Denial of Service (DoS) to the ondemand system. This vulnerability is fixed in 3.1.14 and 4.0.6.

Impact

For European organizations utilizing Open OnDemand as a portal for HPC resource management, this vulnerability poses a risk of service disruption. HPC environments are critical for research institutions, universities, and industries relying on computational resources for scientific simulations, data analysis, and engineering tasks. A successful exploitation could lead to denial of service, halting access to HPC resources and delaying critical workloads. This can impact research timelines, operational efficiency, and potentially lead to financial losses or reputational damage. Since ondemand is often deployed in multi-user environments, malicious or careless users could intentionally or unintentionally trigger this vulnerability, affecting all users of the system. The lack of confidentiality impact reduces risk of data leakage, but the availability impact is significant in environments where HPC portals are central to operations. Additionally, recovery from a DoS caused by log flooding may require administrative intervention and system restarts, increasing downtime.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-779Logging of Excessive Data (opens in a new tab)
Base weaknessLikelihood of exploit: Low
The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.
Architecture and Design
Suppress large numbers of duplicate log messages and replace them with periodic summaries. For example, syslog may include an entry that states "last message repeated X times" when recording repeated events.
Architecture and Design
Support a maximum size for the log file that can be controlled by the administrator. If the maximum size is reached, the admin should be notified. Also, consider reducing functionality of the product.
Implementation
Adjust configurations appropriately when the product is transitioned from a debug state to production.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Jul 2025, 20:57 UTC

WeaknessesCWE-400, CWE-779

Technical details

References

Community reviews

Related threats