# CVE-2026-56581: HCL MyCloud was affected with Cookie Attribute Path Not Set

> Missing cookie path attribute in HCL MyCloud increases risk of unauthorized access to session data or authentication tokens.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/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:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-592r-85ww-g563

## What is CVE-2026-56581?

CVE-2026-56581 is a low-severity vulnerability in HCLSoftware MyCloud, published on 21 Jul 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 MyCloud was affected with Cookie Attribute Path Not Set. It may increase the risk of unauthorized access to session data or authentication tokens.

Weakness: CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute)

## Which versions are affected by CVE-2026-56581?

It affects 1 product.


Products: Hcltech Dryice Mycloud.

## How do I fix CVE-2026-56581?

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

## Is CVE-2026-56581 being exploited?

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

## Other vulnerabilities in HCLSoftware MyCloud

- [CVE-2023-23346](https://insights.sbomify.com/CVE-2023-23346/): Use of a broken cryptographic algorithm affects HCL DRYiCE MyCloud (medium 6.4)
- [CVE-2024-30150](https://insights.sbomify.com/CVE-2024-30150/): An unauthenticated privilege escalation vulnerability affects HCL MyCloud (medium 5.3)
- [CVE-2026-56577](https://insights.sbomify.com/CVE-2026-56577/): HCL MyCloud affected by Weak Password Policy (low 3.1)
- [CVE-2026-56579](https://insights.sbomify.com/CVE-2026-56579/): HCL MyCloud was affected with Exposure of Sensitive Information to an Unauthorized Actor. (low 3.1)
- [CVE-2026-56582](https://insights.sbomify.com/CVE-2026-56582/): HCL MyCloud was affected with SSL/TLS Protocol Affected with LUCKY13 Vulnerability. (low 3.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56581 and fix it if it is affected.

What it is: CVE-2026-56581 is a low-severity vulnerability in HCLSoftware MyCloud, published on 21 Jul 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-2026-56581 in the wild and no public exploit code.

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

## Sources

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

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