StreampipesApplication · Apache
CVE-2025-47411
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA user with a legitimate non-administrator account can exploit a vulnerability in the user ID creation mechanism in Apache StreamPipes that allows them to swap the username of an existing user with that of an administrator. This vulnerability allows an attacker to gain administrative control over the application by manipulating JWT tokens, which can lead to data tampering, unauthorized access and other security issues. This issue affects Apache StreamPipes: through 0.97.0. Users are recommended to upgrade to version 0.98.0, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache StreamPipes through version 0.97.0 contains a privilege escalation vulnerability in its user ID creation mechanism that allows non-administrator users to swap their username with that of an administrator. By manipulating the username during user creation, attackers can trigger a collision or overwrite that causes their JWT tokens to be issued with administrator privileges, granting full administrative control over the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
StreampipesApplication
>= 0.69.0, < 0.98.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Apache StreamPipes versionCheck the StreamPipes version by inspecting the deployed artifacts, configuration files, or the application's About/Version endpoint. Common locations include the pom.xml, package.json, or a version manifest in the deployment directory.Affected if The installed version is 0.69.0 or higher but below 0.98.0, placing it within the affected range.
-
Verify JWT token generation for non-administrator accountsCreate a test non-administrator user account or examine existing non-admin user tokens. Inspect the JWT payload (after decoding) to confirm whether any non-admin users unexpectedly hold administrative roles or privileges.Affected if Non-administrator users possess JWT tokens containing administrator-level role claims or permissions.
-
Audit user accounts for username collisions or duplicatesQuery the user database or user configuration to list all registered usernames. Look for accounts where usernames match administrative accounts exactly or differ only by special characters, whitespace, or case variations.Affected if Multiple user records exist with identical or suspiciously similar usernames, particularly if they correspond to administrator accounts.
-
Review authentication logs for user creation anomaliesExamine authentication and user management logs for events involving user creation, especially any failed creation attempts followed by successful ones with manipulated usernames, or unexpected admin role assignments.Affected if Logs show user creation events where usernames were manipulated or where non-admin accounts were granted elevated privileges outside normal administrative workflows.
A user is affected if they are running Apache StreamPipes between versions 0.69.0 and 0.97.0 inclusive, and either non-administrator accounts have administrative JWT claims, duplicate/similar usernames to admins exist, or user creation logs show anomalous privilege escalation patterns.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.98.0
Upgrade Apache StreamPipes to version 0.98.0 or later to obtain the fix for this vulnerability.
0.98.0
- Identify the current Apache StreamPipes version in use (must be >= 0.69.0 and < 0.98.0)
- Backup all existing data, configurations, and databases
- Stop the running StreamPipes instance
- Upgrade to Apache StreamPipes version 0.98.0 using the standard upgrade procedure for your deployment method
- Verify the upgrade was successful by checking the version number
- Restart the StreamPipes service
- Validate that user authentication and authorization are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streampipes
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47411 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data