← Back to results
Vulnerability record · public intelligence
CVE-2023-31975
LOW

CVE-2023-31975

Published May 9, 2023 · Updated Nov 3, 2026

Severity · CVSSLOW · Not scored
Known exploitationNot listed
EPSS / likelihood0.47%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

yasm v1.3.0 was discovered to contain a memory leak via the function yasm_intnum_copy at /libyasm/intnum.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

yasm v1.3.0 was discovered to contain a memory leak via the function yasm_intnum_copy at /libyasm/intnum.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. GitHub advisory ↗
  2. [oss-security] 20230620 CVE-2023-31975: memory leak in yasm ↗
  3. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  4. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  5. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  6. [oss-security] 20230622 Re: CVE-2023-31975: memory leak in yasm ↗
  7. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  8. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  9. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  10. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  11. [oss-security] 20230621 Re: CVE-2023-31975: memory leak in yasm ↗
  12. [oss-security] 20230622 Re: CVE-2023-31975: memory leak in yasm ↗

Record history

Published May 9, 2023 · Last refreshed Nov 3, 2026

Related intelligence
Browse all vulnerabilities →
CVE-2026-110458LOW

CVE-2026-110458

Related through FIRST-EPSS and CVE-LIST-V5 evidence

A malicious actor with access to the network and under certain conditions could exploit a Path Traversal vulnerability found in UniFi Protect AI Key to create or truncate files on the device.

CVE-2026-110624LOW

Papermerge Core through 3.5.3 Missing Authorization via /tags/all and /document-types/all

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Papermerge Core through 3.5.3 Missing Authorization via /tags/all and /document-types/all

CVE-2026-110604LOW

Mini-XML 4.0.0 through 4.0.6 Stack Out-of-Bounds Write via mxml_strtod()

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Mini-XML 4.0.0 through 4.0.6 Stack Out-of-Bounds Write via mxml_strtod()

CVE-2026-11240LOW

CVE-2026-11240

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Insufficient validation of untrusted input in Loader in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Low)