{"answers":{"affected":"3 open source packages ship an affected version, including github.com/Anipaleja/nginx-defender.","exploited":"There is no known exploitation of CVE-2025-55740 in the wild and no public exploit code.","fix":"Upgrade github.com/Anipaleja/nginx-defender to 1.5.0 or later.","what":"CVE-2025-55740 is a medium-severity vulnerability in Anipaleja nginx-defender, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55740 and fix it if it is affected.\n\nWhat it is: CVE-2025-55740 is a medium-severity vulnerability in Anipaleja nginx-defender, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-55740 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/Anipaleja/nginx-defender (Go): affected all versions; fixed in 1.5.0\n- github.com/Anipaleja/nginx-defender (Go): affected all versions; fixed in 1.5.0\n- github.com/Anipaleja/nginx-defender (Go): affected all versions; fixed in 1.5.0\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-2025-55740/ (Markdown: https://insights.sbomify.com/CVE-2025-55740/index.md)","id":"CVE-2025-55740","markdown":"https://insights.sbomify.com/CVE-2025-55740/index.md","name":"CVE-2025-55740","record":{"aliases":["GHSA-pr72-8fxw-xx22","GO-2025-3896"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WAF and threat detection","requires_auth":"none","summary":"Attackers can gain administrative control of nginx-defender deployments using default credentials found in example configuration files.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1392","name":"Use of Default Credentials"}],"description":"nginx-defender is a high-performance, enterprise-grade Web Application Firewall (WAF) and threat detection system engineered for modern web infrastructure. This is a configuration vulnerability affecting nginx-defender deployments. Example configuration files\nconfig.yaml and docker-compose.yml contain default credentials (default_password: \"change_me_please\", GF_SECURITY_ADMIN_PASSWORD=admin123). If users deploy nginx-defender without changing these defaults, attackers with network access could gain administrative control, bypassing security protections. The issue is addressed in v1.5.0 and later.","ecosystems":["Go"],"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":"Default Credentials in nginx-defender Configuration Files","id":"CVE-2025-55740","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"unopim/unopim allows unauthorized product deletion via mass-delete endpoint","id":"CVE-2025-55741"},"packages":[{"ecosystem":"Go","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"github.com/Anipaleja/nginx-defender","purl":null,"source":"GHSA-pr72-8fxw-xx22"},{"ecosystem":"Go","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"github.com/Anipaleja/nginx-defender","purl":"pkg:golang/github.com/Anipaleja/nginx-defender","source":"GHSA-pr72-8fxw-xx22"},{"ecosystem":"Go","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"github.com/Anipaleja/nginx-defender","purl":"pkg:golang/github.com/Anipaleja/nginx-defender","source":"GO-2025-3896"}],"prev":{"headline":"api: Shared OAuth Signing Key Between Different Instances","id":"CVE-2025-55739"},"products":["nginx-defender"],"published":"2025-08-19","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"2025-08-19","vendors":["Anipaleja"]},"summary":"Attackers can gain administrative control of nginx-defender deployments using default credentials found in example configuration files.","url":"https://insights.sbomify.com/CVE-2025-55740/"}