# CVE-2025-68833: HCL Hive is affected by use of a cryptographic primitive with a risky implementation

> Attackers can bypass access controls due to weak cryptographic implementation in HCL Hive Keycloak IAM, gaining unauthorized access to resources.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-x278-8xqr-3rx2

## What is CVE-2025-68833?

CVE-2025-68833 is a medium-severity vulnerability in HCLSoftware HCL Hive, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HCL Hive Keycloak IAM Instance is affected by insufficient granularity of access control which could allow an attacker unauthorized access to resources.

Weakness: CWE-1240 (Use of a Cryptographic Primitive with a Risky Implementation)

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


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

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

## Is CVE-2025-68833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68833 is a medium-severity vulnerability in HCLSoftware HCL Hive, published on 24 Aug 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-2025-68833 in the wild and no public exploit code.

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

## Sources

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

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