Excessive secret inheritance in OpenCTI CI pipeline
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Privilege escalation
- Confidentiality · integrity · availability
- High · High · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-6qpm-8p4w-xfm5. Fix status from GitHub. Impact type from CWE-269.
Summary
OpenCTI's ci-main GitHub Actions workflow passes all repository secrets to eight reusable workflows through secrets: inherit, and references third-party actions by mutable tags instead of commit SHAs (CWE-269). Affected are OpenCTI from 6.8.14 before 7.260807.0 and OCTI LTS 7.260309.0 before 7.260309.0-lts.8. A compromised called workflow or tag-referenced action could read CI secrets during a CI run, but the issue is in the CI/CD pipeline and not the deployed platform.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary The project's `ci-main` GitHub Actions workflow passed `secrets: inherit` to eight reusable workflows, giving each of them the full set of repository secrets instead of only the ones it needs. In addition, third-party GitHub Actions used in the CI/CD pipeline were referenced by mutable version tags rather than immutable commit SHAs. A bug or compromise in a called workflow or a referenced action could therefore expose the project's CI secrets (CICD-SEC-4). ### Impact Over-broad exposure of CI secrets. If a called reusable workflow or a third-party action referenced by tag were compromised, it could read every repository secret available to the calling workflow during a CI run. The issue affects the project's CI/CD pipeline, not the deployed platform. We are not aware of any exploitation. ### Patches Fixed in OpenCTI **7.260807.0**. Reusable workflows now receive only the specific secrets they need, and all third-party GitHub Actions are pinned to immutable commit SHAs ([#17487](https://github.com/OpenCTI-Platform/opencti/pull/17487), [#17519](https://github.com/OpenCTI-Platform/opencti/pull/17519)). The same CI changes were applied to the `lts/7.260309.0` branch and are included in **7.260309.0-lts.8**. The `lts/7.260811.0` branch was created after the fix and was never affected. ### Workarounds None needed for OpenCTI users, as the issue is in the project's CI configuration and not in the deployed platform.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | OpenCTI | >= 6.8.14, < 7.260807.0 | >= 7.260807.0 | Patch available | GHSA-6qpm-8p4w-xfm5 |
| — | OCTI LTS 7.260309.0 | < 7.260309.0-lts.8 | >= 7.260309.0-lts.8 | Patch available | GHSA-6qpm-8p4w-xfm5 |
- OpenCTI Vendor— Affected >= 6.8.14, < 7.260807.0 Fixed in >= 7.260807.0 Patch available GHSA-6qpm-8p4w-xfm5
- OCTI LTS 7.260309.0 Vendor— Affected < 7.260309.0-lts.8 Fixed in >= 7.260309.0-lts.8 Patch available GHSA-6qpm-8p4w-xfm5
Remediation
Upgrade OpenCTI to 7.260807.0 or later and OCTI LTS 7.260309.0 to 7.260309.0-lts.8 or later. The fixes are in pull requests #17487 and #17519 of the OpenCTI repository. The lts/7.260811.0 branch was created after the fix and is not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-6qpm-8p4w-xfm5 OpenCTI Fixed in >= 7.260807.0 Advisory →
- Fix · GHSA-6qpm-8p4w-xfm5 OCTI LTS 7.260309.0 Fixed in >= 7.260309.0-lts.8 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-6qpm-8p4w-xfm5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences