Advisory record · GHSA-p373-jqfm-j6wr

Shinken Solutions Shinken Monitoring vulnerable to Incorrect Access Control

CVSS 9.8 CriticalCriticalEPSS 0.031 · 87th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
shinkenPyPI<=2.4.3No fixed version yet
Identifiers
GHSA-p373-jqfm-j6wr · CVE-2022-37298 · PYSEC-2026-540
Weakness (CWE)
CWE-287
Published
29 Jun 2026
Updated
1 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Shinken versions up to and including 2.4.3 are vulnerable to incorrect access control. The weak authentication in the SafeUnpickler class, which handles objects sent from monitoring nodes to the Shinken server, can be abused by an attacker who can reach the server over the network. The source gives few details on the exact steps or impact. No fix is listed.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H OSV
  • CISA KEV Not listed.
  • EPSS 0.031, the 87th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.