KubePi session fixation attack allows an attacker to hijack a legitimate user session.

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-22479: 0.41% estimated exploitation activity in the next 30 days; percentile 35.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A session fixation attack allows an attacker to hijack a legitimate user session. The attack investigates a flaw in how the online application handles the session ID, especially the susceptible web application. Affected Version <= v1.6.3 Patches The vulnerability has been fixed in v1.6.4. https://github.com/KubeOperator/KubePi/commit/1e9c550356c1a425a742480efcf743d373e98dcb : A session fixation attack allows an attacker to hijack a legitimate user session. Workarounds It is recommended to upgrade the version to v1.6.4. For more information If you have any questions or comments about this advisory, please open an issue. This vulnerability is reported by sachinh09 from huntr.dev.

Published by the source

9 Jan 2023, 21:57 UTC

Last modified by the source

21 Jul 2023, 18:02 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v4w5-r2xc-7f8h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-22479

Advisory: KubePi session fixation attack allows an attacker to hijack a legitimate user session.
IDs: CVE-2023-22479, GHSA-v4w5-r2xc-7f8h
Record: https://patchnext.com/advisories/cve-2023-22479 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/KubeOperator/kubepi 1.6.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/KubeOperator/kubepi: affected <= 1.6.3; fixed in 1.6.4

## Suggested inspection (read-only)
- Go github.com/KubeOperator/kubepi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/KubeOperator/kubepi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v4w5-r2xc-7f8h (GitHub-reviewed advisory GHSA-v4w5-r2xc-7f8h lists affected ranges: Go github.com/KubeOperator/kubepi >=0 <=1.6.3)

Commands are suggestions: review each one before running it.