# CVE-2025-62182: File upload in Pega Infinity

> Privileged users can upload malicious files in Pega Customer Service Framework, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-479w-285r-73xg

## What is CVE-2025-62182?

CVE-2025-62182 is a medium-severity vulnerability in Pegasystems Pega Infinity, published on 13 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pega Customer Service Framework versions 8.7.0 through 25.1.0 are affected by a Unrestricted file upload vulnerability, where a privileged user could potentially upload a malicious file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-62182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62182 is a medium-severity vulnerability in Pegasystems Pega Infinity, published on 13 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62182 in the wild and no public exploit code.

Affected product: Pegasystems Pega Infinity. 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-62182/ (Markdown: https://insights.sbomify.com/CVE-2025-62182/index.md)
```

## Sources

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

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