Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8

Remote Code Execution in com.bstek.uflo:uflo-core

CVE-2022-25894GHSA-8m9f-c5p9-wqch

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven com.bstek.uflo:uflo-core

    Affected
    <= 2.1.5
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-25894: 2.57% estimated exploitation activity in the next 30 days; percentile 85.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of the package com.bstek.uflo:uflo-core are vulnerable to Remote Code Execution (RCE) in the ExpressionContextImpl class via jexl.createExpression(expression).evaluate(context); functionality, due to improper user input validation.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8m9f-c5p9-wqch

Agent brief

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

# Patch Next advisory brief: CVE-2022-25894

Advisory: Remote Code Execution in com.bstek.uflo:uflo-core
IDs: CVE-2022-25894, GHSA-8m9f-c5p9-wqch
Record: https://patchnext.com/advisories/cve-2022-25894 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.bstek.uflo:uflo-core: affected <= 2.1.5

## Suggested inspection (read-only)
- Maven com.bstek.uflo:uflo-core: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.bstek.uflo:uflo-core.
- 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-8m9f-c5p9-wqch (GitHub-reviewed advisory GHSA-8m9f-c5p9-wqch lists affected ranges: Maven com.bstek.uflo:uflo-core >=0 <=2.1.5)

Commands are suggestions: review each one before running it.

Loading voting…