LiveActive security incident?Get immediate response
CVE Record

CVE-2025-46398: Xfig: fig2dev stack-overflow via read_objects

In xfig diagramming tool, a stack-overflow while running fig2dev allows memory corruption via local input manipulation via read_objects function.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-46398 is a local memory-corruption flaw in fig2dev, associated with xfig/transfig. A crafted or manipulated local input file can trigger a stack overflow in read_objects. The main business concern is integrity impact on systems that process Fig diagram files, especially automated conversion hosts.

Executive priority

Treat this as a moderate operational risk. It is not evidenced as actively exploited, but systems that transform user-provided diagrams should be patched or isolated because the recorded impact is high integrity compromise.

Technical view

The issue is classified as CWE-121 stack-based buffer overflow. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact recorded.

Likely exposure

Exposure is most likely where transfig or fig2dev is installed on Red Hat Enterprise Linux 6, 7, 8, or 9, or where xfig-related tooling processes local .fig input. Risk increases if conversion workflows accept files from users or external sources.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described attack requires local input manipulation while running fig2dev. No remote exploitation path is established in the supplied evidence.

Researcher notes

The source bundle identifies read_objects and stack overflow behavior but does not include fixed versions, detailed root cause, or exploit maturity. Validation should focus on package presence and data-flow exposure rather than speculative product scope.

Mitigation direction

  • Check Red Hat and Debian guidance for fixed package availability.
  • Update transfig, fig2dev, or xfig packages through trusted vendor channels.
  • Avoid processing untrusted Fig files until vendor remediation is applied.
  • Remove the package from systems that do not need Fig conversion.
  • Run conversion jobs with least privilege and filesystem isolation.

Validation and detection

  • Inventory systems for installed transfig, fig2dev, or xfig packages.
  • Prioritize RHEL 6, 7, 8, and 9 hosts using transfig.
  • Identify automated jobs that process user-supplied Fig files.
  • Confirm vendor advisory status before marking assets remediated.
  • Review package versions after updates against vendor guidance.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-121: 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 lookup
cve · low confidence lookup

CVE-2025-46398 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N1.83.6redhat

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2025-46398Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. Source timelineredhat

    Made public.

  4. Source timelineredhat

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorxfigxfig, 0unaffected
Red HatRed Hat Enterprise Linux 6transfigaffected
Red HatRed Hat Enterprise Linux 7transfigaffected
Red HatRed Hat Enterprise Linux 8transfigaffected
Red HatRed Hat Enterprise Linux 9transfigaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.