Memory Safety Issue when using patch or merge on state and assign the result back to state

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Affected versions of this crate maintains references to memory that might have been freed already. If affects the following two tremor-script language constructs: A Merge where we assign the result back to the target expression and the expression to be merged needs to reference the event: A Patch where we assign the result back to the target expression and the patch operations used need to reference the event: For constructs like this (it doesnt matter what is references in the expression to be merged or the patch operations) an optimization was applied to manipulate the target value in-place, instead of cloning it. Our Value struct which underpins all event data in tremor-script, is representing as borrowed strings beef::Cow<'lifetime, str that reference the actual Vec<u8 the event is based upon. We keep the raw byte-array next to the event structure inside our Event struct as a self-referential struct, so we make sure that the structured Value and its references are valid across…

Published by the source

17 Jun 2022, 00:27 UTC

Last modified by the source

13 Jun 2023, 21:47 UTC

Source last checked

26 Oct 2026, 15:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3pp4-64mp-9cg9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-3pp4-64mp-9cg9

Advisory: Memory Safety Issue when using `patch` or `merge` on `state` and assign the result back to `state`
IDs: GHSA-3pp4-64mp-9cg9
Record: https://patchnext.com/advisories/ghsa-3pp4-64mp-9cg9 (revision 1, source checked 26 Oct 2026, 15:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tremor-script 0.11.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tremor-script: affected >= 0.7.2, < 0.11.6; fixed in 0.11.6

## Suggested inspection (read-only)
- crates.io tremor-script: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tremor-script.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3pp4-64mp-9cg9 (GitHub-reviewed advisory GHSA-3pp4-64mp-9cg9 lists affected ranges: crates.io tremor-script >=0.7.2 <0.11.6)

Commands are suggestions: review each one before running it.