fluent Fluentd up to 1.19.2 Monitor Agent Plugin /api/plugins.json missing initialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.54 |
Summary
A vulnerability was found in fluent Fluentd up to 1.19.2. It has been rated as problematic. Impacted is an unknown function of the file /api/plugins.json of the component Monitor Agent Plugin. This manipulation causes missing initialization. This vulnerability is handled as CVE-2026-44025. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability has been found in fluent Fluentd up to 1.19.2 and classified as problematic. Affected by this vulnerability is an unknown function of the file /api/plugins.json of the component Monitor Agent Plugin. The manipulation with an unknown input leads to a missing initialization vulnerability. The CWE definition for the vulnerability is CWE-456. The product does not initialize critical variables, which causes the execution environment to use unexpected values. As an impact it is known to affect confidentiality. The summary by CVE is:
Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Prior to 1.19.3, Fluentd's Monitor Agent plugin in_monitor_agent exposes internal metrics and plugin information via a REST API, and responses from /api/plugins.json and related endpoints unintentionally include internal instance variables that may contain database passwords, API keys, or cloud credentials. This issue is fixed in version 1.19.3.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-44025 since 05/04/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
By approaching the search of inurl:api/plugins.json it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.19.3 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/fluent/fluentd/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing initializationCWE: CWE-456 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Fluentd 1.19.3
Timeline
05/04/2026 CVE reserved07/08/2026 VulDB entry created
07/09/2026 Advisory disclosed
07/09/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-44025 (🔒)
GCVE (CVE): GCVE-0-2026-44025
GCVE (VulDB): GCVE-100-377041
Entry
Created: 07/09/2026 00:20Changes: 07/09/2026 00:20 (54)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.