CVE-2026-22096
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 · uneditedThe webserver running on port 8090 does not require authentication. This allows for sensitive information leakage such as configured passwords, or uploading files through different endpoints.
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 · moderate confidenceThe webserver running on port 8090 lacks authentication requirements, allowing unauthenticated attackers to access sensitive information such as configured passwords and upload files through various endpoints. This represents a complete authentication bypass enabling both information disclosure and potential remote code execution via file upload.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Verify port 8090 is listeningRun 'netstat -tuln | grep 8090' or 'ss -tuln | grep 8090' to confirm the webserver port is open and listeningAffected if Port 8090 is open and accepting connections - the service is exposed
-
Confirm webserver accepts unauthenticated requestsSend an HTTP request to port 8090 without any authentication headers: 'curl -v http://<target>:8090/' or 'curl -v http://localhost:8090/'Affected if The server returns HTTP 200 or other successful response without requiring authentication credentials
-
Check for sensitive information disclosureAccess common endpoints that may expose passwords or configuration: 'curl http://<target>:8090/config', 'curl http://<target>:8090/settings', 'curl http://<target>:8090/passwords'Affected if These endpoints return sensitive data such as passwords, API keys, or configuration details without authentication
-
Detect unauthenticated file upload capabilityTest file upload endpoints: 'curl -X POST -F 'file=@/etc/passwd' http://<target>:8090/upload' or similar upload pathsAffected if File upload endpoints accept files without any authentication requirement
-
Review webserver authentication configurationInspect configuration files (e.g., server.xml, httpd.conf, application.yml) for authentication settings on port 8090, looking for 'auth', 'security', 'require' directivesAffected if No authentication mechanism is configured or enforced for the webserver on port 8090
If port 8090 is exposed and the webserver accepts requests and returns sensitive data or allows file uploads without any authentication, the environment is affected by this CVE.
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.
From vendor dataEnable authentication on the webserver, restrict network access to port 8090 through firewall rules or network segmentation, audit all endpoints for file upload functionality, and rotate any exposed credentials.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22096 — 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-2026-22096 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