CVE-2026-4819
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 · uneditedIn Search Guard FLX versions from 1.0.0 up to 4.0.1, the audit logging feature might log user credentials from users logging into Kibana.
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 audit logging feature in Search Guard FLX versions 1.0.0 through 4.0.1 has a flaw where user credentials (usernames and/or passwords) from Kibana login attempts are inadvertently written to audit log files. This creates an information disclosure vulnerability where anyone with access to the audit logs can obtain valid user credentials.
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>= 1.0.0, < 4.1.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Search Guard FLX versionQuery the Search Guard plugin version via Elasticsearch API endpoint or inspect the installed Search Guard FLX package in the Elasticsearch plugins directoryAffected if The installed version falls within 1.0.0 through 4.0.1 inclusive
-
Confirm audit logging is activeCheck the Search Guard configuration file (sg_audit.yml) or use the Search Guard REST API to verify that audit logging is enabledAffected if Audit logging is turned on in the Search Guard configuration
-
Inspect audit logs for plaintext credentialsReview the Search Guard audit log files in the Elasticsearch logs directory, searching for Kibana authentication entries that contain username and password fields in plaintextAffected if Audit logs contain visible plaintext credentials from Kibana login attempts
You are affected if Search Guard FLX version 1.0.0-4.0.1 is installed, audit logging is enabled, and plaintext credentials appear in the audit logs.
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 · scoped4.1.0
Upgrade Search Guard FLX to a version beyond 4.0.1 that addresses this issue; if no fixed version is available, disable audit logging or reconfigure it to exclude authentication credential data, and rotate any credentials that may have been exposed in existing logs.
Search Guard FLX 4.1.0
- 1. Identify all Search Guard FLX installations in your environment that are running versions >= 1.0.0 and < 4.1.0
- 2. Review your current audit logging configuration to confirm credential logging is occurring
- 3. Plan for a maintenance window to perform the upgrade
- 4. Back up your current Search Guard FLX configuration
- 5. Upgrade Search Guard FLX to version 4.1.0 or later
- 6. After upgrade, verify that audit logs no longer contain plaintext user credentials
- 7. Confirm the audit logging feature is functioning correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4819 — 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-4819 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