How many CVEs have patched parseDatasetFileS3Key?

1 published CVEs changed parseDatasetFileS3Key in labring/FastGPT, in 2 distinct patches totalling 39 changed lines, between 2026 and 2026.

What is the latest CVE that changed parseDatasetFileS3Key?

CVE-2026-55418 (FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)), published 2026-07-07, changed lines 1 to 39 of packages/service/common/s3/sources/dataset/key.ts.

How does parseDatasetFileS3Key compare to the rest of labring/FastGPT?

labring/FastGPT has 17 CVEs with a located fix in total; 1 of them changed parseDatasetFileS3Key.

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Labring
Fastgpt
ParseDatasetFileS3Key

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Labring
Fastgpt
ParseDatasetFileS3Key

parseDatasetFileS3Key in labring/FastGPT: Patched by 1 CVEs

labring/FastGPT

Function

parseDatasetFileS3Key

Name: parseDatasetFileS3Key in labring/FastGPT: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

packages/service/common/s3/sources/dataset/key.ts

Last patched July 7, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

parseDatasetFileS3Key in labring/FastGPT was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 39 lines in total.

labring/FastGPT has 17 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

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

FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)
CVE-2026-55418 · lines 1–39 · +39 −0
High · CVSS 8.6
EPSS 0.5%2026-07-07

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

Monitor FastGPT CVEs

Other hotspots in the repository

Functions in labring/FastGPT changed by the most CVE fixes.

handler3 CVEs · projects/app/src/pages/api/core/app/mcpTools/getTools.ts handler3 CVEs · projects/app/src/pages/api/core/app/mcpTools/runTool.ts string2 CVEs · packages/service/env.ts handler2 CVEs · projects/app/src/pages/api/core/app/httpTools/runTool.ts onSuccess2 CVEs · projects/app/src/pageComponents/login/LoginForm/WechatForm.tsx object2 CVEs · packages/global/openapi/support/user/account/password/api.ts

All patched functions in labring/FastGPT

Frequently asked questions

Common questions about CVE fixes to parseDatasetFileS3Key.

How many CVEs have patched parseDatasetFileS3Key?: 1 published CVEs changed parseDatasetFileS3Key in labring/FastGPT, in 2 distinct patches totalling 39 changed lines, between 2026 and 2026.
What is the latest CVE that changed parseDatasetFileS3Key?: CVE-2026-55418 (FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)), published 2026-07-07, changed lines 1 to 39 of packages/service/common/s3/sources/dataset/key.ts.
How does parseDatasetFileS3Key compare to the rest of labring/FastGPT?: labring/FastGPT has 17 CVEs with a located fix in total; 1 of them changed parseDatasetFileS3Key.
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

packages/service/common/s3/sources/dataset/key.ts on GitHub (opens in a new tab)
All patched functions in labring/FastGPT
Patched functions directory

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

Track labring/FastGPT 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

On this page

Overview
CVEs that patched it
Other hotspots in the repository
FAQ
References