How many CVEs have patched shouldCreateSkippedCommitStatusForFilteredWorkflow?

4 published CVEs changed shouldCreateSkippedCommitStatusForFilteredWorkflow in go-gitea/gitea, in 2 distinct patches totalling 28 changed lines, between 2026 and 2026.

What is the latest CVE that changed shouldCreateSkippedCommitStatusForFilteredWorkflow?

CVE-2026-71184 (Gitea fork workflow approval bypass through review events), published 2026-10-14, changed lines 421 to 434 of services/actions/notifier_helper.go.

How does shouldCreateSkippedCommitStatusForFilteredWorkflow compare to the rest of go-gitea/gitea?

go-gitea/gitea has 162 CVEs with a located fix in total; 4 of them changed shouldCreateSkippedCommitStatusForFilteredWorkflow.

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
Go Gitea
Gitea
ShouldCreateSkippedCommitStatusForFilteredWorkflow

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
Go Gitea
Gitea
ShouldCreateSkippedCommitStatusForFilteredWorkflow

shouldCreateSkippedCommitStatusForFilteredWorkflow in go-gitea/gitea: Patched by 4 CVEs

go-gitea/gitea

Function

shouldCreateSkippedCommitStatusForFilteredWorkflow

Name: shouldCreateSkippedCommitStatusForFilteredWorkflow in go-gitea/gitea: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

services/actions/notifier_helper.go

Last patched October 14, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

shouldCreateSkippedCommitStatusForFilteredWorkflow in go-gitea/gitea was changed by 4 published CVE fixes in 2026, in 2 distinct patches that added or removed 28 lines in total.

go-gitea/gitea has 162 CVEs with a located fix in total, so 2% of them touched this function.

CVEs that patched it

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

Gitea fork workflow approval bypass through review events
CVE-2026-71184 · lines 421–434 · +7 −0
High · CVSS 8.8
EPSS 0.5%2026-10-14
Gitea fork workflow approval bypass through concurrency cancellation
CVE-2026-66877 · lines 421–434 · +7 −0
High · CVSS 8.1
EPSS 0.4%2026-10-14
Gitea required Actions check bypass through skipped workflows
CVE-2026-66874 · lines 421–434 · +7 −0
Medium · CVSS 6.5
EPSS 0.3%2026-10-14
Gitea private reusable workflow disclosure to fork runs
CVE-2026-63792 · lines 421–434 · +7 −0
Medium · CVSS 5.3
EPSS 0.4%2026-10-14

Get an alert when the next CVE fix lands in go-gitea/gitea, with the patched functions.

Monitor gitea CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1buildApproveAndInsertRunservices/actions/notifier_helper.go5 CVEs · 3 patches2026
2newPullRequestReviewNotifyInputservices/actions/notifier_helper.go4 CVEs · 2 patches2026
3getApprovalUsersservices/actions/notifier_helper.go4 CVEs · 1 patches2026
4detectScopedWorkflowsForSourceservices/actions/notifier_helper.go1 CVEs · 2 patches2026
5handleWorkflowsservices/actions/notifier_helper.go1 CVEs · 2 patches2026
6ifNeedApprovalservices/actions/notifier_helper.go1 CVEs · 2 patches2026
7ifNeedApprovalWithservices/actions/notifier_helper.go1 CVEs · 2 patches2026
8detectAndHandleScopedWorkflowsservices/actions/notifier_helper.go1 CVEs · 2 patches2026

Other hotspots in the repository

Functions in go-gitea/gitea changed by the most CVE fixes.

Routes22 CVEs · routers/api/v1/api.go hookPostReceiveUpdateRepoByOptions10 CVEs · routers/private/hook_post_receive.go Clone9 CVEs · modules/git/repo.go attachmentBelongsToRepoOrIssue9 CVEs · routers/api/v1/repo/issue_attachment.go Close9 CVEs · routers/api/v1/repo/file.go GetRawFileOrLFS9 CVEs · routers/api/v1/repo/file.go

All patched functions in go-gitea/gitea

Frequently asked questions

Common questions about CVE fixes to shouldCreateSkippedCommitStatusForFilteredWorkflow.

How many CVEs have patched shouldCreateSkippedCommitStatusForFilteredWorkflow?: 4 published CVEs changed shouldCreateSkippedCommitStatusForFilteredWorkflow in go-gitea/gitea, in 2 distinct patches totalling 28 changed lines, between 2026 and 2026.
What is the latest CVE that changed shouldCreateSkippedCommitStatusForFilteredWorkflow?: CVE-2026-71184 (Gitea fork workflow approval bypass through review events), published 2026-10-14, changed lines 421 to 434 of services/actions/notifier_helper.go.
How does shouldCreateSkippedCommitStatusForFilteredWorkflow compare to the rest of go-gitea/gitea?: go-gitea/gitea has 162 CVEs with a located fix in total; 4 of them changed shouldCreateSkippedCommitStatusForFilteredWorkflow.
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

services/actions/notifier_helper.go on GitHub (opens in a new tab)
All patched functions in go-gitea/gitea
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 go-gitea/gitea 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 functions in these files
Other hotspots in the repository
FAQ
References