Security readout for executives and security teams
Plain-English summary
CVE-2025-46397 is a high-severity stack overflow in xfig’s bezier_spline handling. Red Hat tracks affected transfig packages on several RHEL 8 and 9 channels. The risk is mainly systems where users or automated workflows process untrusted figure files, because successful exploitation could allow code execution with high confidentiality, integrity, and availability impact.
Executive priority
Treat this as a patch-priority issue for affected Linux systems that handle graphics or document conversion inputs. It is high impact but local in attack vector, so urgency depends on whether untrusted users or submitted files can reach xfig/transfig processing paths.
Technical view
The issue is reported as CWE-120 in xfig, allowing possible code execution through local input manipulation in bezier_spline. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, unchanged scope, and high CIA impact. Red Hat lists affected transfig builds for RHEL 8, RHEL 9, and RHEL 9 EUS variants.
Likely exposure
Exposure is most likely on Linux workstations, build hosts, document conversion systems, or engineering pipelines with xfig/transfig installed. Red Hat explicitly lists affected transfig packages for RHEL 8, RHEL 9, RHEL 9.4 EUS, and RHEL 9.6 EUS. RHEL 6 and 7 status is listed as unknown in the provided data.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. The attack vector is local, so internet-facing risk is indirect unless a service or workflow processes attacker-supplied xfig/transfig input. The record states possible code execution, but provides no exploit details in the supplied evidence.
Researcher notes
Evidence is strongest for Red Hat transfig package impact and CVSS characterization. The provided bundle identifies the vulnerable area as bezier_spline and CWE-120 but does not include patch mechanics, exploit status, or detailed root-cause analysis. Avoid assuming impact beyond listed packages without vendor confirmation.
Mitigation direction
- Apply relevant Red Hat errata updates for affected RHEL channels.
- Check Debian LTS and other vendor guidance for non-Red Hat packages.
- Prioritize systems processing untrusted figure or conversion inputs.
- Restrict untrusted local file processing until patched.
- Review unsupported or unknown-status RHEL 6 and 7 deployments.
Validation and detection
- Inventory installed xfig and transfig packages across Linux assets.
- Compare installed package versions against Red Hat affected versions and errata.
- Confirm RHEL channel, CRB, and EUS subscription exposure.
- Check whether automated workflows process untrusted figure files.
- Document vendor status where package exposure remains unknown.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-46397 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9redhatVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:0700CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:0704CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:0705CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:0756CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2025-46397CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2362058CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://sourceforge.net/p/mcj/tickets/192/CVE reference, redhat
- https://lists.debian.org/debian-lts-announce/2025/04/msg00043.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.