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

> A remote attacker can cause a denial of service in Eprosima Micro-XREC-DDS Agent by sending a packet with an invalid Boolean field value.

- **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:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-c43r-cxjc-jq23

## What is CVE-2025-63548?

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

### Official description

An issue in Eprosima Micro-XREC-DDS Agent v.3.0.1 allows a remote attacker to cause a denial of service via a packet specially crafted to bear a non-valid value in any Boolean field.

Weakness: CWE-241 (Improper Handling of Unexpected Data Type)

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


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

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

## Is CVE-2025-63548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63548 is a high-severity denial of service vulnerability in n/a, published on 1 May 2026. 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-63548 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-63548/ (Markdown: https://insights.sbomify.com/CVE-2025-63548/index.md)
```

## Sources

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

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