# Deserialization vulnerability in Helix workflow and REST

Advisory record · `GHSA-jhcr-hph9-g7wm`

- **Identifiers:** `GHSA-jhcr-hph9-g7wm` · `CVE-2023-38647`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 26 Jul 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Jul 2023, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.helix:helix-core` (Maven): affected `<1.3.0`; fixed in `1.3.0`
- `org.apache.helix:helix-rest` (Maven): affected `<1.3.0`; fixed in `1.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Helix core and Helix REST (Maven org.apache.helix:helix-core and helix-rest) before 1.3.0 are vulnerable to unsafe deserialization of YAML input through SnakeYAML. An attacker who can supply YAML for Helix REST start or workflow creation could load a remote JAR and run code, likely leading to remote code execution. Upgrade helix-core and helix-rest to 1.3.0 or later; until then, stop using YAML-based configuration and workflow creation.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.020, the 80th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jhcr-hph9-g7wm)

## Sources

- [GitHub Advisory Database: GHSA-jhcr-hph9-g7wm](https://github.com/advisories/GHSA-jhcr-hph9-g7wm)
- [OSV: GHSA-jhcr-hph9-g7wm](https://osv.dev/vulnerability/GHSA-jhcr-hph9-g7wm)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-38647>
- <https://github.com/apache/helix/commit/09d210fa29b18f3b4de8d32f2369dc2b31f71f43>
- <https://github.com/apache/helix/commit/eabfda26b18c72f4f945dcaac5756665c6a2cdac>
- <https://lists.apache.org/thread/zyqxhv0lc2z9w3tgr8ttrdy2zfh5jvc4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jhcr-hph9-g7wm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jhcr-hph9-g7wm/>. Everything for agents: <https://agentprime.io/llms.txt>.
