FKIE_CVE-2026-24891
Vulnerability from fkie_nvd - Published: 2026-02-20 18:25 - Updated: 2026-06-17 10:23| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/openITCOCKPIT/openITCOCKPIT/releases/tag/openITCOCKPIT-5.4.0 | Product, Release Notes | |
| security-advisories@github.com | https://github.com/openITCOCKPIT/openITCOCKPIT/security/advisories/GHSA-x4mq-8gfg-frc4 | Exploit, Mitigation, Vendor Advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| it-novum | openitcockpit | * |
{
"affected": [
{
"affectedData": [
{
"product": "openITCOCKPIT",
"vendor": "openITCOCKPIT",
"versions": [
{
"status": "affected",
"version": "\u003c 5.4.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:it-novum:openitcockpit:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D1602A3F-8FC6-43BE-948E-BE5E574DEDF9",
"versionEndExcluding": "5.4.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "openITCOCKPIT is an open source monitoring tool built for different monitoring engines like Nagios, Naemon and Prometheus. Versions 5.3.1 and below contain an unsafe deserialization sink in the Gearman worker implementation. The worker function registered as oitc_gearman calls PHP\u0027s unserialize() on job payloads without enforcing class restrictions or validating data origin. While the intended deployment assumes only trusted internal components enqueue Gearman jobs, this trust boundary is not enforced in application code. In environments where the Gearman service or worker is exposed to untrusted systems, an attacker may submit crafted serialized payloads to trigger PHP Object Injection in the worker process. This vulnerability is exploitable when Gearman listens on non-local interfaces, network access to TCP/4730 is unrestricted, or untrusted systems can enqueue jobs. Default, correctly hardened deployments may not be immediately exploitable, but the unsafe sink remains present in code regardless of deployment configuration. Enforcing this trust boundary in code would significantly reduce risk and prevent exploitation in misconfigured environments. This issue has been fixed in version 5.4.0."
},
{
"lang": "es",
"value": "openITCOCKPIT es una herramienta de monitorizaci\u00f3n de c\u00f3digo abierto dise\u00f1ada para diferentes motores de monitorizaci\u00f3n como Nagios, Naemon y Prometheus. Las versiones 5.3.1 e inferiores contienen un sumidero de deserializaci\u00f3n insegura en la implementaci\u00f3n del worker de Gearman. La funci\u00f3n worker registrada como oitc_gearman llama a unserialize() de PHP en las cargas \u00fatiles de los trabajos sin aplicar restricciones de clase ni validar el origen de los datos. Aunque el despliegue previsto asume que solo los componentes internos de confianza encolan trabajos de Gearman, este l\u00edmite de confianza no se aplica en el c\u00f3digo de la aplicaci\u00f3n. En entornos donde el servicio o worker de Gearman est\u00e1 expuesto a sistemas no confiables, un atacante puede enviar cargas \u00fatiles serializadas maliciosas para desencadenar una inyecci\u00f3n de objetos PHP en el proceso del worker. Esta vulnerabilidad es explotable cuando Gearman escucha en interfaces no locales, el acceso a la red a TCP/4730 no est\u00e1 restringido, o los sistemas no confiables pueden encolar trabajos. Los despliegues predeterminados y correctamente reforzados pueden no ser inmediatamente explotables, pero el sumidero inseguro permanece presente en el c\u00f3digo independientemente de la configuraci\u00f3n del despliegue. Aplicar este l\u00edmite de confianza en el c\u00f3digo reducir\u00eda significativamente el riesgo y evitar\u00eda la explotaci\u00f3n en entornos mal configurados. Este problema ha sido corregido en la versi\u00f3n 5.4.0."
}
],
"id": "CVE-2026-24891",
"lastModified": "2026-06-17T10:23:45.543",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 5.9,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-24891",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-20T18:41:20.604345Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-02-20T18:25:51.143",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Product",
"Release Notes"
],
"url": "https://github.com/openITCOCKPIT/openITCOCKPIT/releases/tag/openITCOCKPIT-5.4.0"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/openITCOCKPIT/openITCOCKPIT/security/advisories/GHSA-x4mq-8gfg-frc4"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-502"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.