How many CVEs have patched _fulfill_params_from_enterprise?

1 published CVEs changed _fulfill_params_from_enterprise in langgenius/dify, in 1 distinct patches totalling 21 changed lines, between 2025 and 2025.

What is the latest CVE that changed _fulfill_params_from_enterprise?

CVE-2025-63387, published 2025-12-18, changed lines 313 to 357 of api/services/feature_service.py.

How does _fulfill_params_from_enterprise compare to the rest of langgenius/dify?

langgenius/dify has 20 CVEs with a located fix in total; 1 of them changed _fulfill_params_from_enterprise.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

langgenius/dify

Function

_fulfill_params_from_enterprise

Name: _fulfill_params_from_enterprise in langgenius/dify: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

api/services/feature_service.py

Last patched December 18, 2025

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

21

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

_fulfill_params_from_enterprise in langgenius/dify was changed by 1 published CVE fixes in 2025, in 1 distinct patches that added or removed 21 lines in total.

langgenius/dify has 20 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _fulfill_params_from_enterprise, newest first, with the lines each fix touched.

CVE-2025-63387
CVE-2025-63387 · lines 313–357 · +8 −13 in 2 hunks
High · CVSS 7.5
EPSS 29.9%2025-12-18

Get an alert when the next CVE fix lands in langgenius/dify, with the patched functions.

Monitor dify CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1get_system_featuresapi/services/feature_service.py1 CVEs · 1 patches2025

Other hotspots in the repository

Functions in langgenius/dify changed by the most CVE fixes.

post4 CVEs · api/controllers/console/app/app.py get3 CVEs · api/controllers/console/auth/data_source_bearer_auth.py put3 CVEs · api/controllers/console/app/app.py delete3 CVEs · api/controllers/console/app/app.py post3 CVEs · api/controllers/console/app/workflow.py get3 CVEs · api/controllers/console/app/workflow.py

All patched functions in langgenius/dify

Frequently asked questions

Common questions about CVE fixes to _fulfill_params_from_enterprise.

How many CVEs have patched _fulfill_params_from_enterprise?: 1 published CVEs changed _fulfill_params_from_enterprise in langgenius/dify, in 1 distinct patches totalling 21 changed lines, between 2025 and 2025.
What is the latest CVE that changed _fulfill_params_from_enterprise?: CVE-2025-63387, published 2025-12-18, changed lines 313 to 357 of api/services/feature_service.py.
How does _fulfill_params_from_enterprise compare to the rest of langgenius/dify?: langgenius/dify has 20 CVEs with a located fix in total; 1 of them changed _fulfill_params_from_enterprise.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track langgenius/dify CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing