Skip to content

← Public intelligence

Maven package

org.apache.wicket:wicket-parent

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Apache Wicket has an Exposure of Sensitive Information to an Unauthorized Actor vulnerability

    CVE-2026-43646 · GHSA-jvv4-8wxx-m5r6

    Affected
    • Maven org.apache.wicket:wicket-parent >= 8.0.0-M1, <= 8.17.0; >= 9.0.0-M1, <= 9.22.0; >= 10.0.0-M1, <= 10.8.0
    Fixed in
    10.9.0· Partial vendor fix
    Issue
    Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Wicket. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, from 9.0.0 through 9.22.0, from 10.0.0 through 10.8.0. Users are recommended to upgrade to version 10.9.0, which fixes the issue.

    Recommended action: Upgrade to 10.9.0; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.1MavenPublished

    Apache Wicket has a Cross-site Scripting issue

    CVE-2026-42509 · GHSA-5x9h-93gp-chpj

    Affected
    • Maven org.apache.wicket:wicket-parent >= 8.0.0-M1, <= 8.17.0; >= 9.0.0-M1, <= 9.22.0; >= 10.0.0-M1, <= 10.8.0
    Fixed in
    10.9.0· Partial vendor fix
    Issue
    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Wicket. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, 9.0.0, from 10.0.0 through 10.8.0. Users are recommended to upgrade to version 10.9.0, which fixes the issue.

    Recommended action: Upgrade to 10.9.0; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →