CVE-2024-22195VulnerabilityPublished 8 Oct 2026Updated 28 Oct 2026

SUSE · Security update 5.2.1 for Multi-Linux Manager Client Tools

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2024-22195· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade SUSE jinja to 3.1.3 when convenient.

Data as of 28 Oct 2026, 19:27 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 3.1.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jinja to 3.1.3.

Affected software

Product	Affected	Fixed in
PyPIjinja`pkg:pypi/jinja`Other threats	Affected <3.1.3	Fixed in 3.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update fixes the following issues: mgr-push was updated to version 5.2.5: - Removed token based authentication mechanism for package_push (bsc#1230949) spacecmd was updated to version 5.2.10: - Pre-filter errata in system_applyerrata to avoid using API calls for all existing errata (bsc#1267261) - Updated translation strings spacewalk-client-tools was updated to version 5.2.7:: - Updated translation strings uyuni-tools was updated to version 5.2.17: Security issues fixed: - CVE-2026-39821: Drop the direct dependency on golang.org/x/net (bsc#1266481) Bug fixes and changes: - Version 5.2.17-0: * Bump the default image tag to 5.2.1 * Reload systemd daemon before restarting services (bsc#1270033) * Check all supported locations for CA file in rotation check script * Detect and fix legacy service file (bsc#1268755) * Use healthcheck cmd from the image (bsc#1273144) - Version 5.2.16-0: * Reverted usage of sdnotify as it causes issues with Podman (bsc#1270399, bsc#1270398) - Version 5.2.15-0: * Added requirement for at least Podman v4.7.2 * Send READY notification to systemd only once healthy (bsc#1263823) - Version 5.2.14-0: * Include the server environment file in the backup (bsc#1268649) * Added mgradm commands for SSL CA and certificate rotation - Version 5.2.13-0: * Check and warn if CA certificate isn't marked as critical * Disable SSL on database during split (bsc#1267980) * Do not call uyuni-postgres-config.sh in mgradm (bsc#1267980) * Check backup status only after database is started (bsc#1262492) venv-salt-minion: - Security issues: * CVE-2026-13346: Fixed an issue where malicious package indexes could install unauthorized files (bsc#1273094) * CVE-2026-0864: Fixed custom configuration injection risks caused by improper line-ending validation (bsc#1269066) * CVE-2026-1502: Fixed web request header manipulation to bypass proxy security protections (bsc#1261969) * CVE-2026-3276: Fixed potential system slow down or freeze when processing crafted Unicode text (bsc#1267581) * CVE-2026-4360: Fixed directory escape risks during archive extraction (bsc#1269959) * CVE-2026-4786: Fixed command injection risks when processing malicious browser links (bsc#1262319) * CVE-2026-6019: Fixed a flaw where cookies could be manipulated to run malicious script (bsc#1262654) * CVE-2026-6100: Fixed crashes or unauthorized code execution during file decompression (bsc#1262098) * CVE-2026-7210: Fixed system freezes triggered by parsing malicious XML files (bsc#1264962) * CVE-2026-7774: Fixed path traversal risks where malicious archives write files outside targets (bsc#1267821) * CVE-2026-8328: Fixed connections being redirected to unsafe systems by compromised FTP servers (bsc#1265268) * CVE-2026-11940: Fixed a bug where extracting malicious archives could overwrite system files (bsc#1268977) * CVE-2026-11972: Fixed infinite loop and system freeze risks during archive decompression (bsc#1269788) * CVE-2026-15308: Fixed crashes when parsing web pages with repetitive, incomplete structures (bsc#1271192) * CVE-2026-8643: Fixed malicious package installs overwriting arbitrary local files (bsc#1266669) * CVE-2026-6357: Fixed package self-updates loading unauthorized modules during install (bsc#1263442) * CVE-2026-3219: Fixed validation failures where combined ZIP archives were not rejected (bsc#1262429) * CVE-2026-1703: Fixed package installations writing files outside target directories (bsc#1257599) * CVE-2024-22195: Fixed HTML template manipulation allowing unauthorized script execution (bsc#1218722) * CVE-2026-45409: Fixed domain name encoding bypass allowing imitation websites (bsc#1265413) * CVE-2026-44431: Fixed data leaks where sensitive headers were sent to external origins (bsc#1265267) * CVE-2026-49825: Fixed missing script cleanup from namespaces in web content (bsc#1270285) * CVE-2026-41066: Fixed leakage of private system data via malicious XML file parsing (bsc#1263254) * CVE-2026-3446: Fixed validation bypasses where hidden excess Base64 data was ignored (bsc#1261970) * CVE-2026-3479: Fixed path traversal risks when loading packages from insecure locations (bsc#1259989) * CVE-2026-27459: Fixed buffer overflow vulnerabilities caused by large cookie headers (bsc#1271428) * CVE-2026-49853: Fixed credentials leakage during redirects to cross-origin servers (bsc#1268395) * CVE-2026-49854: Fixed crashes or unauthorized memory access in compiled components (bsc#1268396) * CVE-2026-49855: Fixed crashes caused by excessively compressed files exhausting memory (bsc#1268397) * CVE-2026-40475: Fixed silent data truncation where hidden null characters bypass checks (bsc#1262803) * CVE-2025-13836: Fixed memory exhaustion risk by limiting HTTP response reading size (bsc#1254400) - Bug fixes and changes: * Updated bundled python module pip to 25.0.1 * Updated bundled python module jinja2 to 3.1.6 * Updated b

GCVE source: db.gcve.eu
Csaf Category: csaf_security_advisory
Csaf Version: 2.0
Publisher: SUSE Product Security Team
Advisory ID: SUSE-SU-2026:4584-1
Vendor Severity: high
CVE Count: 32
Additional Cves: CVE-2025-13836, CVE-2026-0864, CVE-2026-11940, CVE-2026-11972, CVE-2026-13346, CVE-2026-1502, CVE-2026-15308, CVE-2026-1703, CVE-2026-27459, CVE-2026-3219, CVE-2026-3276, CVE-2026-3446, CVE-2026-3479, CVE-2026-39821, CVE-2026-40475, CVE-2026-41066, CVE-2026-4360, CVE-2026-44431, CVE-2026-45409, CVE-2026-4786, CVE-2026-49825, CVE-2026-49853, CVE-2026-49854, CVE-2026-49855, CVE-2026-6019, CVE-2026-6100, CVE-2026-6357, CVE-2026-7210, CVE-2026-7774, CVE-2026-8328, CVE-2026-8643

References

Community reviews

Loading reviews…