Faktory Web Dashboard can lead to denial of service(DOS) via malicious user input

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2023-37279: 0.92% estimated exploitation activity in the next 30 days; percentile 60.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Faktory web dashboard can suffer from denial of service by a crafted malicious url query param days. Details The vulnerability is related to how the backend reads the days URL query parameter in the Faktory web dashboard. The value is used directly without any checks to create a string slice. If a very large value is provided, the backend server ends up using a significant amount of memory and causing it to crash. PoC To reproduce this vulnerability, please follow these steps: Start the Faktory Docker and limit memory usage to 512 megabytes for better demonstration: Send the following request. The Faktory server will exit after a few seconds due to out of memory: Impact Server Availability: The vulnerability can crash the Faktory server, affecting its availability. Denial of Service Risk: Given that the Faktory web dashboard does not require authorization, any entity with internet access to the dashboard could potentially exploit this vulnerability. This unchecked access…

Published by the source

20 Sep 2023, 22:51 UTC

Last modified by the source

12 Nov 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x4hh-vjm7-g2jv

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

# Patch Next advisory brief: CVE-2023-37279

Advisory: Faktory Web Dashboard can lead to denial of service(DOS) via malicious user input
IDs: CVE-2023-37279, GHSA-x4hh-vjm7-g2jv
Record: https://patchnext.com/advisories/cve-2023-37279 (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: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/contribsys/faktory 1.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/contribsys/faktory: affected < 1.8.0; fixed in 1.8.0

## Suggested inspection (read-only)
- Go github.com/contribsys/faktory: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/contribsys/faktory.
- 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-x4hh-vjm7-g2jv (GitHub-reviewed advisory GHSA-x4hh-vjm7-g2jv lists affected ranges: Go github.com/contribsys/faktory >=0 <1.8.0)

Commands are suggestions: review each one before running it.