{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4819 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4819 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 31 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4819 and fix it if it is affected.\n\nWhat it is: CVE-2026-4819 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 31 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4819 in the wild and no public exploit code.\n\nAffected product: floragunn Search Guard FLX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4819/ (Markdown: https://insights.sbomify.com/CVE-2026-4819/index.md)","id":"CVE-2026-4819","markdown":"https://insights.sbomify.com/CVE-2026-4819/index.md","name":"CVE-2026-4819","record":{"aliases":["GHSA-vx77-83rf-gfvg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Search Guard FLX","requires_auth":"high_privilege","summary":"Attackers with access to audit logs can read user credentials logged during Kibana login, requiring audit logging to be enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"floragunn","cpe":[{"product":"flx","vendor":"search-guard"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"In 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Search Guard audit logs can contain under certain conditions user credentials","id":"CVE-2026-4819","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Maximo Application Suite was vulnerable to because Cookie ltpatoken2_\u003cworkspace_name\u003e was not set with secure flag","id":"CVE-2026-4820"},"packages":[],"prev":{"headline":"Some management operations on data streams are not properly restricted when user does not have the necessary privileges","id":"CVE-2026-4818"},"products":["Search Guard FLX"],"published":"2026-03-31","related":[{"cvss_score":6.8,"headline":"Some management operations on data streams are not properly restricted when user does not have the necessary privileges","id":"CVE-2026-4818","kev_date_added":null,"published":"2026-03-31"},{"cvss_score":4.3,"headline":"Open redirect vulnerability in Search Guard Kibana Plugin via manipulated requests","id":"CVE-2026-4799","kev_date_added":null,"published":"2026-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-31","vendors":["floragunn"]},"summary":"Attackers with access to audit logs can read user credentials logged during Kibana login, requiring audit logging to be enabled.","url":"https://insights.sbomify.com/CVE-2026-4819/"}