# CVE-2025-63938: Integer overflow in n/a

> An integer overflow in Tinyproxy's strip_return_port function can lead to denial of service, requiring administrators to upgrade the proxy software.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-63938, GHSA-w547-jc37-w3cr, UBUNTU-CVE-2025-63938

## What is CVE-2025-63938?

CVE-2025-63938 is a medium-severity vulnerability in n/a, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tinyproxy through 1.11.2 contains an integer overflow vulnerability in the strip_return_port() function within src/reqs.c.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Tinyproxy Project Tinyproxy.

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

Upgrade to a fixed version.

## Is CVE-2025-63938 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49606](https://insights.sbomify.com/CVE-2023-49606/): Use after free in Tinyproxy (critical 9.8)
- [CVE-2026-31842](https://insights.sbomify.com/CVE-2026-31842/): Tinyproxy HTTP request parsing desynchronization via case-sensitive Transfer-Encoding handling (high 8.7)
- [CVE-2022-40468](https://insights.sbomify.com/CVE-2022-40468/): Information disclosure in n/a (high 7.5)
- [CVE-2017-11747](https://insights.sbomify.com/CVE-2017-11747/): Privilege escalation in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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