# CVE-2026-46398: HAX CMS Missing Secure Flag on Cookie

> Attackers can steal session tokens via network sniffing because the cookie lacks the Secure flag, potentially leading to account takeover.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 5 Jun 2026

## What is CVE-2026-46398?

CVE-2026-46398 is a high-severity vulnerability in haxtheweb haxcms-php, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HAX CMS helps manage microsite universe with PHP or NodeJs backends. Starting in version 25.0.0 and prior to version 26.0.0, the haxcms_refresh_token cookie is set without the Secure flag. This allows it to be transmitted over unencrypted HTTP, making it vulnerable to theft via packet sniffing on the network. Version 26.0.0 fixes the issue.

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

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


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

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

## Is CVE-2026-46398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46398 is a high-severity vulnerability in haxtheweb haxcms-php, published on 5 Jun 2026. 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-2026-46398 in the wild and no public exploit code.

Affected product: haxtheweb haxcms-php. 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-46398/ (Markdown: https://insights.sbomify.com/CVE-2026-46398/index.md)
```

## Sources

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

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