CVE-2025-58413: A stack-based buffer overflow vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through...
A stack-based buffer overflow vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiSASE 25.3.b allows attacker to execute unauthorized code or commands via specially crafted packets
Security readout for executives and security teams
Plain-English summary
CVE-2025-58413 is a Fortinet FortiOS and FortiSASE memory-safety flaw. A nearby unauthenticated attacker could send crafted packets that may run unauthorized code or commands. The score is medium, but the possible confidentiality, integrity, and availability impact is high.
Executive priority
Prioritize assessment and vendor-guided remediation for Fortinet security infrastructure. The rating is medium because access and complexity constraints apply, but successful exploitation could compromise core network controls and business availability.
Technical view
The issue is a CWE-121 stack-based buffer overflow affecting listed FortiOS releases and FortiSASE 25.3.b. CVSS 3.1 is 6.9 with adjacent-network access, high attack complexity, no privileges, no user interaction, and high CIA impact. The bundle indicates proof-of-concept exploit maturity and workaround remediation level, but gives no details.
Likely exposure
Exposure is most likely in environments running the listed FortiOS versions or FortiSASE 25.3.b where an attacker can reach the vulnerable service from an adjacent network path. Public internet exposure is not established by the provided CVSS vector.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It states the attack uses specially crafted packets and requires adjacent-network access with high attack complexity. Treat exploit availability as limited to the bundle's CVSS exploit maturity signal.
Researcher notes
Do not assume internet-reachable exploitation from the provided data. The key constraints are AV:A and AC:H. The bundle does not provide vulnerable protocol details, exploit steps, fixed versions, or workaround specifics, so validation should focus on version exposure and vendor advisory follow-up.
Mitigation direction
Check Fortinet PSIRT FG-IR-25-632 for fixed releases and any documented workaround.
Upgrade affected FortiOS deployments according to Fortinet guidance.
Confirm FortiSASE 25.3.b remediation steps with Fortinet or service administration guidance.
Reduce adjacent-network reachability to affected systems while remediation is planned.
Track the Siemens advisory if Fortinet products are embedded in Siemens-managed environments.
Validation and detection
Inventory FortiOS and FortiSASE versions against the affected ranges in the CVE record.
Confirm whether any affected interface is reachable from adjacent network segments.
Review Fortinet PSIRT FG-IR-25-632 for exact vulnerable and fixed build mapping.
Check vendor logs and monitoring for unusual packet-triggered crashes or command-execution indicators.
Document systems excluded because their versions are outside the listed affected ranges.
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.
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
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
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.