Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-109431 Overview
CVE-2026-109431 is a missing authorization vulnerability [CWE-639] in Camunda 7 engine-rest task sub-resources. Camunda versions 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 fail to enforce authorization checks on singular read and delete endpoints for task comments and attachments. Authenticated users without any permission grants can access or destroy task data by invoking endpoints such as getAttachment, getAttachmentData, deleteAttachment, and getComment with only a known object ID. The flaw exists in TaskAttachmentResourceImpl and TaskCommentResourceImpl, where list endpoints apply authorization filters but singular endpoints do not.
Critical Impact
Authenticated attackers with zero permissions can read, download, or permanently delete task attachments and comments across the entire Camunda deployment.
Affected Products
- Camunda 7.24.0 through 7.24.13
- Camunda 7.23.0 through 7.23.16
- Camunda engine-rest API component (TaskAttachmentResourceImpl, TaskCommentResourceImpl)
Discovery Timeline
- 2026-10-19 - CVE-2026-109431 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-109431
Vulnerability Analysis
The vulnerability resides in Camunda's REST API layer, specifically the task sub-resource handlers for comments and attachments. Camunda enforces authorization in the engine by filtering results on list endpoints such as GET /task/{id}/attachment and GET /task/{id}/comment. These list endpoints only return items the caller is authorized to view.
The singular endpoints, however, bypass this filtering logic. Methods including getAttachment, getAttachmentData, deleteAttachment, and getComment resolve objects directly by ID and return or delete them without validating caller permissions against the parent task. An authenticated user with no permission grants can therefore read sensitive attachments, download file contents, or permanently remove comments and attachments. The flaw maps to Insecure Direct Object Reference behavior as classified under CWE-639.
Root Cause
The root cause is inconsistent authorization enforcement between list and singular sub-resource endpoints. List endpoints apply authorization-filtered queries, while singular endpoints in TaskAttachmentResourceImpl and TaskCommentResourceImpl resolve objects by primary key without re-checking that the caller has READ or UPDATE permission on the associated task. This asymmetry violates the engine's permission model.
Attack Vector
Exploitation requires network access to the Camunda REST API and valid authenticated credentials with no granted permissions. An attacker enumerates or guesses attachment and comment IDs, then issues direct GET or DELETE requests against the singular task sub-resource paths. Successful requests return attachment metadata, raw attachment payloads, or confirm destructive deletion. Detailed exploitation steps are described in the Codeant Security Research advisory and the VulnCheck Advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-109431
Indicators of Compromise
- Authenticated REST requests to /task/{taskId}/attachment/{attachmentId} or /task/{taskId}/comment/{commentId} from user accounts with no assigned authorizations.
- HTTP 200 responses on singular attachment or comment endpoints followed by no prior successful list endpoint call to the same task.
- Unexpected DELETE requests against /task/{taskId}/attachment/{attachmentId} from low-privilege service accounts.
- Spikes in sequential attachment or comment ID enumeration against the engine-rest API.
Detection Strategies
- Correlate Camunda access logs with the engine authorization table to flag singular sub-resource access by principals lacking task-level permissions.
- Deploy web application firewall rules that log and alert on direct access to task attachment and comment endpoints without a preceding authorized list query.
- Compare EPSS exploitation forecasts and advisory updates against observed request patterns to prioritize investigation.
Monitoring Recommendations
- Enable verbose audit logging for the engine-rest API and ship logs to a centralized SIEM for retention and correlation.
- Alert on bulk DELETE operations against task sub-resources, particularly from accounts that have never created the referenced tasks.
- Monitor authentication logs for new or dormant service accounts suddenly accessing task sub-resource endpoints.
How to Mitigate CVE-2026-109431
Immediate Actions Required
- Upgrade Camunda to version 7.24.14 or 7.23.17 or later as published on the Camunda Enterprise Download portal.
- Audit all REST API user accounts and revoke credentials that are no longer required.
- Review historical access logs for singular task attachment and comment endpoint calls to assess exposure.
- Rotate secrets for any attachments that may have contained credentials or tokens.
Patch Information
Camunda addressed the vulnerability by applying the same authorization-filtered checks used on list endpoints to the singular read and delete endpoints in TaskAttachmentResourceImpl and TaskCommentResourceImpl. Fixed versions are 7.24.14 and 7.23.17. Enterprise customers should obtain patched builds through the official Camunda enterprise download channel.
Workarounds
- Restrict network access to the engine-rest API using a reverse proxy or API gateway that enforces path-level allow lists.
- Block or rate-limit direct access to /task/*/attachment/* and /task/*/comment/* endpoints at the gateway until patches are applied.
- Enforce least-privilege authentication by removing unused REST API users and disabling anonymous or default credentials.
- Treat the mitigation as temporary; apply the vendor patch at the earliest maintenance window.
# Example reverse proxy rule to restrict singular task sub-resource endpoints
location ~ ^/engine-rest/task/[^/]+/(attachment|comment)/[^/]+$ {
allow 10.0.0.0/8; # trusted internal management network
deny all;
proxy_pass http://camunda_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

