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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
Sources
- GitHub Advisory Database: GHSA-p373-jqfm-j6wr
- OSV: GHSA-p373-jqfm-j6wr
- nvd.nist.gov/vuln/detail/CVE-2022-37298
- github.com/naparuba/shinken/commit/2dae40fd1e713aec9e1966a0ab7a580b9180cff2
- github.com/dbyio/cve-2022-37298
- github.com/naparuba/shinken
- pypi.org/project/shinken
- github.com/advisories/GHSA-p373-jqfm-j6wr