Information Exposure Affecting n8n-oci-entrypoint package, versions <2.25.7-r0
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-N8NOCIENTRYPOINT-17662956
- published29 Jun 2026
- disclosed23 Jun 2026
Introduced: 23 Jun 2026
NewCVE-2026-54305 (opens in a new tab)How to fix?
Upgrade Minimos:latest n8n-oci-entrypoint to version 2.25.7-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream n8n-oci-entrypoint package and not the n8n-oci-entrypoint package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, three EE endpoints used by the Dynamic Credentials feature accepted any authenticated n8n session without performing per-resource ownership or scope checks on the target workflow or credential. An authenticated user with no project membership or credential sharing relationship could enumerate credential identifiers, names, and types referenced by any private workflow in the instance, initiate an OAuth authorization flow against another user's credential to overwrite its stored tokens with tokens bound to an account they control, or revoke another user's stored credential tokens entirely. Workflows relying on a hijacked credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of integrations. Token revocation would break affected workflows. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.