Search results

https://github.com/yaml/libyaml/issues/321#issuecomment-3703927906

Status: Open.

#322 In yaml/libyaml;

· soekhantpaing130-dev opened on Jan 1, 2026

Efootball

Status: Open.

#321 In yaml/libyaml;

· soekhantpaing130-dev opened on Jan 1, 2026

$ ./bootstrap $ ./configure $ make # make install

Status: Open.

#320 In yaml/libyaml;

· soekhantpaing130-dev opened on Jan 1, 2026

Konami

Status: Open.

#319 In yaml/libyaml;

· soekhantpaing130-dev opened on Nov 25, 2025

[BUG] Scanner API: infinite-loop risk for some clients...

Status: Open.

#318 In yaml/libyaml;

· rootkid19 opened on Nov 6, 2025

CMake version needs updating

Status: Open.

#317 In yaml/libyaml;

· ImOnALampshade opened on Jul 29, 2025

[BUG] A SEGV in <code>yaml_free</code> at <code>src/api.c:53:14</code>

Status: Open.

#312 In yaml/libyaml;

· JJLeo opened on May 14, 2025

Memory Leak in api.c

Status: Open.

#309 In yaml/libyaml;

· zhaohuanqdcn opened on May 7, 2025

YAML_FLOW_MAPPING_START_TOKEN

Status: Open.

#307 In yaml/libyaml;

· bkaraujo opened on Mar 21, 2025

CVE-2024-35325

Status: Open.

#303 In yaml/libyaml;

· perlpunk opened on Jul 17, 2024

CVE-2024-35326, CVE-2024-35328, CVE-2024-35329

Status: Open.

#302 In yaml/libyaml;

· perlpunk opened on Jul 17, 2024

How is this CVE-2024-35329 affected?

Status: Open.

#298 In yaml/libyaml;

· zhuofeng6 opened on Jun 12, 2024