# CVE-2025-62341: HCL Connections is vulnerable to server-side request forgery (SSRF)

> An attacker can exploit SSRF in HCL Connections to send unauthorized requests, potentially leading to information disclosure or security bypass.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-pvr3-52wm-4cjw

## What is CVE-2025-62341?

CVE-2025-62341 is a low-severity server-side request forgery vulnerability in HCLSoftware Connections, published on 26 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

HCL Connections is vulnerable to server-side request forgery (SSRF) when an internal server is compromised possibly allowing an attacker to send unauthorized requests in certain scenarios leading to information disclosure or security bypass.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-62341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62341 is a low-severity server-side request forgery vulnerability in HCLSoftware Connections, published on 26 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62341 in the wild and no public exploit code.

Affected product: HCLSoftware Connections. 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-62341/ (Markdown: https://insights.sbomify.com/CVE-2025-62341/index.md)
```

## Sources

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

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