{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27981 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27981 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27981 is a high-severity vulnerability in sysadminsmedia homebox, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27981 and fix it if it is affected.\n\nWhat it is: CVE-2026-27981 is a high-severity vulnerability in sysadminsmedia homebox, published on 3 Mar 2026. 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-2026-27981 in the wild and no public exploit code.\n\nAffected product: sysadminsmedia homebox. 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-27981/ (Markdown: https://insights.sbomify.com/CVE-2026-27981/index.md)","id":"CVE-2026-27981","markdown":"https://insights.sbomify.com/CVE-2026-27981/index.md","name":"CVE-2026-27981","record":{"aliases":["GHSA-j86g-v96v-jpp3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HomeBox inventory system","requires_auth":"none","summary":"Attackers can bypass authentication rate limits by spoofing IP headers, enabling brute-force attacks against HomeBox.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"homebox","vendor":"sysadminsmedia"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"HomeBox is a home inventory and organization system. Prior to 0.24.0, the authentication rate limiter (authRateLimiter) tracks failed attempts per client IP. It determines the client IP by reading, 1. X-Real-IP header, 2. First entry of X-Forwarded-For header, and 3. r.RemoteAddr (TCP connection address). These headers were read unconditionally. An attacker connecting directly to Homebox could forge any value in X-Real-IP, effectively getting a fresh rate limit identity per request. There is a TrustProxy option in the configuration (Options.TrustProxy, default false), but this option was never read by any middleware or rate limiter code. Additionally, chi's middleware.RealIP was applied unconditionally in main.go, overwriting r.RemoteAddr with the forged header value before it reaches any handler. This vulnerability is fixed in 0.24.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"HomeBox has an Auth Rate Limit Bypass via IP Spoofing","id":"CVE-2026-27981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"django-allauth has an open redirect vulnerability","id":"CVE-2026-27982"},"packages":[],"prev":{"headline":"Next.js: Unbounded next/image disk cache growth can exhaust storage","id":"CVE-2026-27980"},"products":["homebox"],"published":"2026-03-03","related":[{"cvss_score":8.1,"headline":"HomeBox has Unauthorized API Access via Retained defaultGroup ID After Group Access Revocation","id":"CVE-2026-40196","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":5,"headline":"HomeBox affected by Blind SSRF","id":"CVE-2026-27600","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":4.6,"headline":"HomeBox affected by Stored XSS via HTML/SVG Attachment Upload","id":"CVE-2026-26272","kev_date_added":null,"published":"2026-03-03"}],"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":"total"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["sysadminsmedia"]},"summary":"Attackers can bypass authentication rate limits by spoofing IP headers, enabling brute-force attacks against HomeBox.","url":"https://insights.sbomify.com/CVE-2026-27981/"}