Scan Another

CVE Scan for langfuse/langfuse-worker:3

Docker image vulnerability scanner

12 Known Vulnerabilities in this Docker Image

0
Critical
4
High
5
Medium
3
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2026-4800highpkg:npm/lodash@4.17.23>=4.0.0,<=4.17.234.18.08.1

Impact

The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink.

When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time.

Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function().

Patches

Users should upgrade to version 4.18.0.

The fix applies two changes:

  1. Validate importsKeys against the existing reForbiddenIdentifierChars regex (same check already used for the variable option)
  2. Replace assignInWith with assignWith when merging imports, so only own properties are enumerated

Workarounds

Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.

Relevance:

Based on the description of CVE-2026-4800, the vulnerability's relevance depends on whether the `langfuse-worker` image utilizes the specific underlying library or component affected by this flaw. It would be critical in scenarios where the worker processes untrusted input or external data that could trigger the vulnerability, potentially leading to remote code execution or a denial of service within the container. For normal usage, the impact is likely low unless the worker’s core logic or its environment variables are directly exposed to the specific attack vector described. (Note: Relevance analysis is automatically generated and may require verification.)

Package URL(s):
  • pkg:npm/lodash@4.17.23
CVE-2026-35209highpkg:npm/defu@6.1.4<=6.1.46.1.57.5
CVE-2026-4867highpkg:npm/path-to-regexp@0.1.12<0.1.130.1.137.5
CVE-2026-4926highpkg:npm/path-to-regexp@8.3.0>=8.0.0,<8.4.08.4.07.5
CVE-2025-60876mediumbusybox<=1.37.0-r30not fixed6.5
CVE-2026-2950mediumpkg:npm/lodash@4.17.23<=4.17.234.18.06.5
CVE-2026-33750mediumpkg:npm/brace-expansion@2.0.2>=2.0.0,<2.0.35.0.56.5
CVE-2026-33349mediumpkg:npm/fast-xml-parser@5.5.6>=4.0.0-beta.3,<=5.5.65.5.75.9
CVE-2026-4923mediumpkg:npm/path-to-regexp@8.3.0>=8.0.0,<8.4.08.4.05.9
CVE-2026-2391lowpkg:npm/qs@6.14.1>=6.7.0,<=6.14.16.14.23.7

Severity Levels

Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.

Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.

Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.

Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.

Severity is not determined, informational, or negligible. Review based on context.

Sliplane Icon
About Sliplane

Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.

Try Sliplane for free

About the CVE Scanner

What is a CVE?

CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.

About the CVE Scanner

The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.

How the CVE Scanner Works

The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.

Why CVE Scanning is Essential for Your Docker Images

With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.

Benefits of CVE Scanning

  • Enhanced Security: Detect and mitigate vulnerabilities before they are exploited.
  • Compliance: Meet industry standards and regulatory requirements for secure software.
  • Proactive Maintenance: Stay ahead of potential threats by addressing vulnerabilities early.

The Importance of Patching Docker Images

Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.

Want to deploy this image?

Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.

Connect Github