# CVE-2025-63662: Information disclosure in n/a

> Unauthorized attackers can access sensitive information via insecure permissions in the GT Edge AI Platform API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2025
- **Updated:** 23 Dec 2025
- **Also known as:** GHSA-rcqf-2rrp-6p54

## What is CVE-2025-63662?

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

### Official description

Insecure permissions in the /api/v1/agents API of GT Edge AI Platform before v2.0.10-dev allows unauthorized attackers to access sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Gtedge Gt Edge Ai.

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

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

## Is CVE-2025-63662 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63665](https://insights.sbomify.com/CVE-2025-63665/): Code injection in n/a (critical 9.8)
- [CVE-2025-63663](https://insights.sbomify.com/CVE-2025-63663/): Missing authorization in n/a (high 7.5)
- [CVE-2025-63664](https://insights.sbomify.com/CVE-2025-63664/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63662 is a high-severity vulnerability in n/a, published on 22 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-63662 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-63662/ (Markdown: https://insights.sbomify.com/CVE-2025-63662/index.md)
```

## Sources

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

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