{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-71378 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71378 is a medium-severity vulnerability in Apache Wicket, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-71378 and fix it if it is affected.\n\nWhat it is: CVE-2026-71378 is a medium-severity vulnerability in Apache Wicket, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-71378 in the wild and no public exploit code.\n\nAffected product: Apache Wicket. 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-71378/ (Markdown: https://insights.sbomify.com/CVE-2026-71378/index.md)","id":"CVE-2026-71378","markdown":"https://insights.sbomify.com/CVE-2026-71378/index.md","name":"CVE-2026-71378","record":{"aliases":["GHSA-298h-94gv-3jfv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"low_privilege","summary":"Attackers can bypass CSRF protections in Apache Wicket to execute actions on behalf of authenticated users via cross-site navigations or sibling origins.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"wicket","vendor":"apache"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"ResourceIsolationRequestCycleListener protects a Wicket application against cross-site request forgery by rejecting requests that a resource isolation policy judges to come from another origin. Its default policy, FetchMetadataResourceIsolationPolicy, was derived from a reference implementation written to guard static resources, and it inherited two allowances that are unsafe when the thing being guarded is an action on a page:\n  *  Every \"simple top-level navigation\" was allowed. Any GET request carrying Sec-Fetch-Mode: navigate whose Sec-Fetch-Dest was neither object nor embed was allowed, whatever Sec-Fetch-Site said — including cross-site. Wicket invokes component listeners (Link.onClick(), form submits, behaviour callbacks) through ordinary GET navigations, so a page under an attacker's control could navigate the victim's browser to a listener URL and have that listener run inside the victim's authenticated session. Browsers send SameSite=Lax cookies — the effective default when no SameSite attribute is set — on cross-site top-level GET navigations, so the victim's session cookie accompanied the request.\n  *  Sec-Fetch-Site: same-site was allowed unconditionally. That value means the same registrable domain and scheme but a different origin — another subdomain or another port. Any sibling origin could therefore invoke any listener by any method, POST form submits included, and cookies are always sent on same-site requests regardless of SameSite. A hostile sibling origin obtained through a subdomain takeover, through delegated user content, or through an XSS elsewhere on the site could act as the authenticated user.\nUsers are recommended to upgrade to version 9.24.0 or 10.11.0, which fix the issue.\nAffected versions\n\n  *  Apache Wicket 9.1.0 through 9.23.0\n  *  Apache Wicket 10.0.0 through 10.10.0\n\nNot affected\n\nAny release older than 9.1.0:\n  *  Apache Wicket 8.x (8.0.0 through 8.17.0). The resource isolation classes do not exist in the 8.x line, which offers only the Origin/Referer-based CsrfPreventionRequestCycleListener. No 8.x release requires a fix.\n  *  Apache Wicket 9.0.0. ResourceIsolationRequestCycleListener and FetchMetadataResourceIsolationPolicy were introduced by WICKET-6786 and first shipped in 9.1.0 (released 2020-10-07).","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":"Apache Wicket: Cross-Site Request Forgery (CSRF) protection bypass in ResourceIsolationRequestCycleListener","id":"CVE-2026-71378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Toptech TMS7 and TopHAT Files or Directories Accessible to External Parties","id":"CVE-2026-71379"},"packages":[],"prev":{"headline":"Command Argument Injection Vulnerability in Cosminexus Component Container","id":"CVE-2026-71377"},"products":["Apache Wicket"],"published":"2026-08-31","related":[{"cvss_score":9.8,"headline":"Apache Wicket: Remote code execution via XSLT injection","id":"CVE-2024-36522","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":9.1,"headline":"Apache Wicket: possible session fixation using AuthenticatedWebSession","id":"CVE-2026-40010","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":9.1,"headline":"Deserialization in n/a","id":"CVE-2016-6793","kev_date_added":null,"published":"2017-07-14"},{"cvss_score":8.8,"headline":"Apache Wicket vulnerable to CSRF attacks","id":"CVE-2016-6806","kev_date_added":null,"published":"2017-10-02"},{"cvss_score":7.5,"headline":"Apache Wicket: Configured file upload limits are not enforced when the multipart request has already been parsed","id":"CVE-2026-71257","kev_date_added":null,"published":"2026-08-31"},{"cvss_score":7.5,"headline":"Apache Wicket: crafted URLs can bypass PackageResourceGuard","id":"CVE-2026-43646","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.5,"headline":"DNS proxy and possible amplification attack","id":"CVE-2021-23937","kev_date_added":null,"published":"2021-05-25"}],"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-08-31","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass CSRF protections in Apache Wicket to execute actions on behalf of authenticated users via cross-site navigations or sibling origins.","url":"https://insights.sbomify.com/CVE-2026-71378/"}