CVE-2026-76821: OpenCTI: User-Controlled ReDoS in JSON Ingestion Mapper

Published Sep 15, 2026
·
Updated

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the JSON ingestion mapper's extractWithRegexp formula function compiled a user-supplied regular expression with the JavaScript RegExp engine in opencti-platform/opencti-graphql/src/parser/json-mapper.ts without validating its complexity. An authenticated user with JSON mapper creation permission could provide a catastrophically backtracking pattern and matching ingestion input, blocking the Node.js event loop and making the GraphQL API unavailable to all users. Scheduled ingestion could repeatedly execute the malicious mapper without additional attacker action, and recovery could require disabling the mapper and restarting the process. The issue affects availability and does not expose or modify data. This issue is fixed in version 7.260706.0.

Affected Software

1 affected component
opencti-platform/opencti-graphql<7.260706.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade opencti-platform/opencti-graphql to a version that resolves this vulnerability.

    Fixed in 7.260706.0

Event History

Sep 15, 2026
CVE Published
via MITRE·07:38 PM
Data Sourced
via MITRE·07:38 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated OpenCTI user must have permission to create JSON mappers. Exploitation also requires supplying both a catastrophically backtracking regular expression and ingestion input that triggers the expensive match.

2

What is the operational impact?

A successful pattern can block the Node.js event loop, making the GraphQL API unavailable to all users. The issue affects availability only; the provided information does not indicate data exposure or modification.

3

Can the outage persist without further attacker activity?

Yes. If the malicious mapper is used by scheduled ingestion, it can be executed repeatedly without additional attacker action. Recovery may require disabling the mapper and restarting the affected process.

4

What should be done if an immediate upgrade is not possible?

Disable suspected or untrusted JSON mappers, particularly those containing user-supplied regular expressions, and stop scheduled ingestions that invoke them. Restart the process after disabling a mapper that has blocked the event loop.

5

Which versions are fixed?

The issue is fixed in version 7.260706.0. Versions prior to 7.260706.0 are affected according to the provided information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203