Advisory record · GHSA-jhcr-hph9-g7wm

Deserialization vulnerability in Helix workflow and REST

CVSS 9.8 CriticalCriticalEPSS 0.020 · 80th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

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.

PackageEcosystemAffectedFixed in
org.apache.helix:helix-coreMaven<1.3.01.3.0
org.apache.helix:helix-restMaven<1.3.01.3.0
Identifiers
GHSA-jhcr-hph9-g7wm · CVE-2023-38647
Weakness (CWE)
CWE-502
Published
26 Jul 2023
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 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

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

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.