# CVE-2025-61258: Denial of service in n/a

> Attackers can cause denial of service in OutSystems Platform Server via crafted content-length mismatches, though the vendor cannot reproduce the issue.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-g823-f2hp-hrjr

## What is CVE-2025-61258?

CVE-2025-61258 is a high-severity denial of service vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Outsystems Platform Server 11.18.1.37828 allows attackers to cause a denial of service via a crafted content-length value mismatching the body length. NOTE: the Supplier indicates that they are unable to reproduce this.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2025-61258?

It affects 1 product.


Products: Outsystems Platform Server.

## How do I fix CVE-2025-61258?

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

## Is CVE-2025-61258 being exploited?

There is no known exploitation of CVE-2025-61258 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61258 and fix it if it is affected.

What it is: CVE-2025-61258 is a high-severity denial of service vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61258 in the wild and no public exploit code.

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-2025-61258/ (Markdown: https://insights.sbomify.com/CVE-2025-61258/index.md)
```

## Sources

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

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