GHSA-72F5-RR8C-R6GR
Vulnerability from github – Published: 2026-06-26 16:36 – Updated: 2026-06-26 16:36The 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:
- Avoid Dynamic Hostnames
-
Do not use the placeholder in the endpoint parameter as hostname.
-
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.
-
Restrict allowed hosts
- Inject filter to accept allowed hosts in placeholders explicitly if possible.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.19.2"
},
"package": {
"ecosystem": "RubyGems",
"name": "fluentd"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.19.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-44161"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-26T16:36:11Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "The `out_http` output plugin allows the use of placeholders (such as `${tag}`) in the `endpoint` configuration parameter.\nIt 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.\n\n### Impact\nThis vulnerability allows for a **Server-Side Request Forgery (SSRF)** attack.\nAn 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`).\n\n### Patches\nv1.19.3\n\n### Workarounds\nIf an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:\n\n1. Avoid Dynamic Hostnames\n * Do not use the placeholder in the endpoint parameter as hostname.\n\n2. Restrict Network Access \n * Use firewall rules (e.g., iptables, AWS Security Groups) to block the Fluentd node from accessing sensitive internal IP addresses, specifically the cloud provider\u0027s metadata service and other internal microservices that Fluentd does not explicitly need to access.\n\n3. Restrict allowed hosts\n * Inject filter to accept allowed hosts in placeholders explicitly if possible.",
"id": "GHSA-72f5-rr8c-r6gr",
"modified": "2026-06-26T16:36:11Z",
"published": "2026-06-26T16:36:11Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fluent/fluentd/security/advisories/GHSA-72f5-rr8c-r6gr"
},
{
"type": "PACKAGE",
"url": "https://github.com/fluent/fluentd"
},
{
"type": "WEB",
"url": "https://github.com/fluent/fluentd/releases/tag/v1.19.3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "Fluentd is Vulnerable to Server-Side Request Forgery (SSRF) via Placeholder Expansion in `out_http`"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.