NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Silverpeas mishandles the "Personal space" feature that is selected when no componentId is setGHSA-qv8h-rqr3-mph9

MEDIUMFix: Silverpeas/Silverpeas-Core@caa6e6d

GHSA-qv8h-rqr3-mph9 is a medium-severity (CVSS 6.5) CWE-36 vulnerability in org.silverpeas.core:silverpeas-core-war. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2026-53698
Published
Updated
Affected
2 pkgs
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qv8h-rqr3-mph9.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.3%0.3%Jul 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.silverpeas.core:silverpeas-core-war☕org.silverpeas.core:silverpeas-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Silverpeas through 6.4.6 mishandles the "Personal space" feature that is selected when no componentId is set.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
☕Mavenorg.silverpeas.core:silverpeas-core-warall versionsNo fix
☕Mavenorg.silverpeas.core:silverpeas-coreall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.silverpeas.core:silverpeas-core-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of org.silverpeas.core:silverpeas-core-war for GHSA-qv8h-rqr3-mph9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Silverpeas through 6.4.6 mishandles the "Personal space" feature that is selected when no componentId is set.
O3 Security · Impact-Aware SCA

Is GHSA-qv8h-rqr3-mph9 in your dependencies?

Find it across Maven, including transitive dependencies.

Silverpeas mishandles the "Personal space" feature that is…