Skip to main content

CVE-2026-44161

HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-06-26 https://github.com/fluent/fluentd GHSA-72f5-rr8c-r6gr
7.2
CVSS 3.1 · Vendor: https://github.com/fluent/fluentd
Share

Severity by source

Vendor (https://github.com/fluent/fluentd) PRIMARY
7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L
vuln.today AI
5.4 MEDIUM

Network and unauthenticated with no UI, but AC:H because exploitation requires a non-default dynamic-hostname out_http config; scope change for SSRF into other systems, limited confidentiality/availability impact, no integrity impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:N

Primary rating from Vendor (https://github.com/fluent/fluentd).

CVSS VectorVendor: https://github.com/fluent/fluentd

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

Lifecycle Timeline

3
Source Code Evidence Fetched
Jun 26, 2026 - 17:22 vuln.today
Analysis Generated
Jun 26, 2026 - 17:22 vuln.today
CVE Published
Jun 26, 2026 - 16:36 cve.org
HIGH 7.2

DescriptionCVE.org

The out_http output plugin allows the use of placeholders (such as ${tag}) in the endpoint configuration parameter. It was discovered that if the placeholder value is derived from untrusted user input, an attacker can maliciously control the destination hostname of the outbound HTTP requests made by Fluentd.

Impact

This vulnerability allows for a Server-Side Request Forgery (SSRF) attack. An unauthenticated attacker can force the Fluentd node to send HTTP requests to arbitrary internal services. This can lead to unauthorized access to internal APIs, data exfiltration, or the compromise of cloud metadata endpoints (e.g., AWS IMDS 169.254.169.254).

Patches

v1.19.3

Workarounds

If an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:

  1. Avoid Dynamic Hostnames
  • Do not use the placeholder in the endpoint parameter as hostname.
  1. Restrict Network Access
  • Use firewall rules (e.g., iptables, AWS Security Groups) to block the Fluentd node from accessing sensitive internal IP addresses, specifically the cloud provider's metadata service and other internal microservices that Fluentd does not explicitly need to access.
  1. Restrict allowed hosts
  • Inject filter to accept allowed hosts in placeholders explicitly if possible.

AnalysisAI

Server-Side Request Forgery in Fluentd's out_http plugin allows unauthenticated attackers to force the Fluentd node to send HTTP requests to arbitrary internal services, potentially accessing cloud metadata, internal APIs, or exfiltrating data. The vulnerability arises when a placeholder in the endpoint configuration is fed with untrusted input. A patch (v1.19.3) is available, but no public exploit or active exploitation has been observed at this time; EPSS indicates a low 0.45% probability of exploitation.

Share

CVE-2026-44161 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy