cve.bz

CVE-2026-123135 langgenius dify: Use of Hard-coded Password

2.1 lowEPSS 0.2%

Low (2.1) in langgenius dify. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability was found in langgenius dify up to 1.18.0/2.0.0-beta.2. Affected by this vulnerability is an unknown functionality of the file api/configs/feature/__init__.py of the component Sandbox Run Handler. The manipulation results in hard-coded credentials. The attack can be launched remotely. The exploit has been made public and could be used.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-259 Use of Hard-coded Password
CWE-798 Use of Hard-coded Credentials
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123135 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123135?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123135?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123135 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
langgenius dify1.0
langgenius dify1.1
langgenius dify1.2
langgenius dify1.3
langgenius dify1.4
langgenius dify1.5
langgenius dify1.6
langgenius dify1.7
langgenius dify1.8
langgenius dify1.9
langgenius dify1.10
langgenius dify1.11
langgenius dify1.12
langgenius dify1.13
langgenius dify1.14
langgenius dify1.15
langgenius dify1.16
langgenius dify1.17
langgenius dify1.18.0
langgenius dify2.0.0-beta.0
langgenius dify2.0.0-beta.1
langgenius dify2.0.0-beta.2

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON