Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

eventing-gitlab vulnerable to denial of service, caused by improper enforcement of the timeout on individual read operations

GHSA-99jv-8292-2hpm

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go knative.dev/eventing-gitlab

    Affected
    <= 0.39.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact The eventing-gitlab cluster-local server doesn't set ReadHeaderTimeout‬‭ which could lead do a DDoS‬ ‭attack, where a large group of users send requests to the server causing the server to hang‬ ‭for long enough to deny it from being available to other users, also know as a Slowloris‬ ‭attack. Patches Fix in v1.12.1 and v1.11.3. Credits The vulnerability was reported by Ada Logics during an ongoing security audit of Knative involving Ada Logics, the Knative maintainers, OSTIF and CNCF.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-99jv-8292-2hpm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-99jv-8292-2hpm

Advisory: eventing-gitlab vulnerable to denial of service, caused by improper enforcement of the timeout on individual read operations
IDs: GHSA-99jv-8292-2hpm
Record: https://patchnext.com/advisories/ghsa-99jv-8292-2hpm (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go knative.dev/eventing-gitlab: affected <= 0.39.0

## Suggested inspection (read-only)
- Go knative.dev/eventing-gitlab: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on knative.dev/eventing-gitlab.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-99jv-8292-2hpm (GitHub-reviewed advisory GHSA-99jv-8292-2hpm lists affected ranges: Go knative.dev/eventing-gitlab >=0 <=0.39.0)

Commands are suggestions: review each one before running it.

Loading voting…