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

> Remote attackers can cause denial of service by exploiting missing request limits in HCLTech GRAGON APIs.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-697w-32m5-f3vq

## What is CVE-2025-63402?

CVE-2025-63402 is a medium-severity denial of service vulnerability in n/a, published on 3 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue in HCL Technologies Limited HCLTech GRAGON before v.7.6.0 allows a remote attacker to execute arbitrary code via APIs do not enforcing limits on the number or size of requests

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Hcltech Dragon.

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

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

## Is CVE-2025-63402 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63401](https://insights.sbomify.com/CVE-2025-63401/): Cross-site scripting in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63402 is a medium-severity denial of service vulnerability in n/a, published on 3 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63402 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-63402/ (Markdown: https://insights.sbomify.com/CVE-2025-63402/index.md)
```

## Sources

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

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