CVE-2025-11683VulnerabilityPublished 29 Jul 2026Updated 17 Sep 2026

SUSE perl-YAML-Syck · Security update for perl-YAML-Syck

Affects SUSE perl-YAML-SyckSource GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2025-11683· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium · fixed in SUSE package updates : update SUSE perl-YAML-Syck when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.470.0

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
SUSEsuse/perl-YAML-Syck`pkg:rpm/suse/perl-YAML-Syck`Other threats	Affected =1.470.0-bp160.1.1	Fixed in–

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

AI-suggested

A security update to perl-YAML-Syck version 1.470.0 is available that fixes these memory-safety vulnerabilities. Users should upgrade to this version or later to remediate the issues. No additional mitigations are indicated beyond applying this official fix.

Description

This security update for perl-YAML-Syck addresses multiple memory-safety vulnerabilities in the libsyck library that are exploitable via the default YAML::Syck::Load() function when processing untrusted input. The fixed issues include out-of-bounds reads and use-after-free conditions that could lead to crashes or potentially other impacts. The update also hardens base64 decoding and enforces maximum depth limits to prevent stack exhaustion from deeply nested inputs.

Impact

These vulnerabilities allow an attacker to cause memory corruption such as out-of-bounds reads and use-after-free conditions when parsing untrusted YAML input using YAML::Syck::Load(). This can lead to remote denial-of-service crashes and potentially other memory safety issues. The vulnerabilities are exploitable without special flags, making the default usage path vulnerable. The maximum depth enforcement also mitigates stack exhaustion attacks from deeply nested inputs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:10 UTC

Technical details

References

Community reviews

Related threats