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

> Attackers can steal session cookies via XSS because the HttpOnly flag is missing, potentially leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** DEBIAN-CVE-2025-26844, GHSA-qjp8-wwq5-32hp, UBUNTU-CVE-2025-26844

## What is CVE-2025-26844?

CVE-2025-26844 is a critical vulnerability in n/a, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Znuny through 7.1.3. A cookie is set without the HttpOnly flag.

Weakness: CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

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

It affects 1 product.


Products: Znuny Znuny.

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

Apply the vendor's patch.

## Is CVE-2025-26844 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-26846](https://insights.sbomify.com/CVE-2025-26846/): An issue was discovered in Znuny before 7.1.4. (critical 9.8)
- [CVE-2025-26845](https://insights.sbomify.com/CVE-2025-26845/): Code injection in n/a (critical 9.8)
- [CVE-2024-32491](https://insights.sbomify.com/CVE-2024-32491/): Path traversal in n/a (critical 9.8)
- [CVE-2025-26847](https://insights.sbomify.com/CVE-2025-26847/): Information disclosure in n/a (critical 9.1)
- [CVE-2024-32493](https://insights.sbomify.com/CVE-2024-32493/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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