Apache Texera unauthorized read and write of workflow execution results
- Exploited
- No known exploitation
- Fix
- Fixed in 1.3.0-incubating
- Who is exposed
- Not reported
Summary
Apache Texera is affected: authenticated users can read or modify other users' workflow execution results. An attacker needs only a valid login to any account on the system.
Written by a model
Original description
Authenticated users can bypass normal controls on the reading and writing of workflow execution results. This allows any authenticated user to read or modify any other user's workflow execution results.
This issue affects Apache Texera (incubating): from 1.1.0-incubating before 1.3.0-incubating.
Users are recommended to upgrade to version 1.3.0-incubating, which fixes the issue.
What to do
Upgrade to a fixed version: 1.3.0-incubating.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-96295 (Apache Texera: Authenticated users can always see and modify other's workflow execution results), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-96295 (entry last updated 2026-11-20):
Affected:
- Apache Software Foundation Apache Texera: from 1.1.0-incubating, fixed in 1.3.0-incubating
Fixed versions: 1.3.0-incubating.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-96295 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-96295 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/xw55mvsfcv3md2f7fjy2b2dyx2ypkv7r
- http://www.openwall.com/lists/oss-security/2026/11/20/4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-96295
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-96295"}.Affected versions
- Apache Software Foundation Apache TexeraFrom 1.1.0-incubating · fixed in 1.3.0-incubating
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/xw55mvsfcv3md2f7fjy2b2dyx2ypkv7r |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-96295 |
| Record | NVD · CVE-2026-96295 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/20/4 |
Questions about CVE-2026-96295
Is CVE-2026-96295 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-96295?
Apache Texera: from 1.1.0-incubating before 1.3.0-incubating.
Source: cve.now feed data
How do I fix CVE-2026-96295?
Upgrade to a fixed version: 1.3.0-incubating.
Source: cve.now feed data
Related
- CVE-2026-133325Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
- CVE-2026-132079Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry
- CVE-2026-110513Apache Iggy: Deleted user's HTTP token authenticates as the account that reuses its user ID
- CVE-2026-128981Apache SeaTunnel Web: Disabled accounts can obtain new login tokens
- CVE-2026-118028Apache Tomcat: RewriteValve [F]/[G]/[R] rule matches do not stop processing
- CVE-2026-116561Apache Tomcat: Jakarta Authentication secureResponse AuthException sends unprotected HTTP 200 response
No corrections so far. Something wrong on this page? Report an error.