{"answers":{"affected":"2 open source packages ship an affected version, including org.graylog2:graylog2-server.","exploited":"There is no known exploitation of CVE-2026-55425 in the wild and no public exploit code.","fix":"Upgrade org.graylog2:graylog2-server to 7.1.4 or later.","what":"CVE-2026-55425 is a medium-severity vulnerability in graylog2-server, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55425 and fix it if it is affected.\n\nWhat it is: CVE-2026-55425 is a medium-severity vulnerability in graylog2-server, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55425 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4\n- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4\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-55425/ (Markdown: https://insights.sbomify.com/CVE-2026-55425/index.md)","id":"CVE-2026-55425","markdown":"https://insights.sbomify.com/CVE-2026-55425/index.md","name":"CVE-2026-55425","record":{"aliases":["GHSA-q79r-r9xg-r863"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Graylog log management","requires_auth":"low_privilege","summary":"Authenticated users can retrieve protected database fields, including password hashes, via the System Catalog titles endpoint.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-213","name":"Exposure of Sensitive Information Due to Incompatible Policies"}],"description":"Graylog is a free and open log management platform. From 7.1.0 until 7.1.4 and 7.2.0-alpha.2, the System Catalog entity titles endpoint in graylog2-server/src/main/java/org/graylog2/rest/resources/system/contentpacks/titles/EntityTitleServiceImpl.java allows an authenticated user to request composite display fields without verifying that every selected field is readable. A user can retrieve protected values, including the password hash on a readable user record; ordinary users are limited to their own permitted records, while administrators can retrieve hashes for all users. This issue is fixed in versions 7.1.4 and 7.2.0-alpha.2.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Graylog: System Catalog titles endpoint can be used to retrieve values of protected database fields","id":"CVE-2026-55425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"linuxfabrik-lib: Local privilege escalation using embedded command","id":"CVE-2026-55426"},"packages":[{"ecosystem":"Maven","fixed":["7.1.4"],"introduced":["7.1.0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":null,"source":"GHSA-q79r-r9xg-r863"},{"ecosystem":"Maven","fixed":["7.1.4"],"introduced":["7.1.0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":"pkg:maven/org.graylog2/graylog2-server","source":"GHSA-q79r-r9xg-r863"}],"prev":{"headline":"Discourse: Topic featured link susceptible to stored XSS","id":"CVE-2026-55424"},"products":["graylog2-server"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-08-31","vendors":["Graylog2"]},"summary":"Authenticated users can retrieve protected database fields, including password hashes, via the System Catalog titles endpoint.","url":"https://insights.sbomify.com/CVE-2026-55425/"}