CVE-2025-59718: A improper verification of cryptographic signature vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8…
Noroxi assessment
Priority: Now (action score 89/100)
- CISA has confirmed exploitation in the wild (Dec 16, 2025). Remediation deadline for US federal agencies: Dec 23, 2025.
- Probability of exploitation in the next 30 days: 68% (FIRST EPSS); higher than 99.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
A improper verification of cryptographic signature vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2.0 through 7.2.11, FortiOS 7.0.0 through 7.0.17, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4.0 through 7.4.10, FortiProxy 7.2.0 through 7.2.14, FortiProxy 7.0.0 through 7.0.21, FortiSwitchManager 7.2.0 through 7.2.6, FortiSwitchManager 7.0.0 through 7.0.5 allows an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML response message.
- Published
- Dec 9, 2025
- Updated
- Oct 15, 2026
- EPSS
- 68.0% · 99th percentile
- CWE
- CWE-347
Report tools
Action score
89
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 20 / 30 · 68.0%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · fortinet
- 9.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Dec 16, 2025. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Dec 23, 2025.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| fortinet | fortiproxy | cpe:2.3:a:fortinet:fortiproxy |
| fortinet | fortiswitchmanager | cpe:2.3:a:fortinet:fortiswitchmanager |
| fortinet | fortios | cpe:2.3:o:fortinet:fortios |
| siemens | ruggedcom ape1808 firmware | cpe:2.3:o:siemens:ruggedcom_ape1808_firmware |
| siemens | ruggedcom ape1808 | cpe:2.3:h:siemens:ruggedcom_ape1808 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (fortinet). Independent of NVD's CPE analysis and usually ahead of it.
Fortinet FortiOS
- 7.6.0 and later · up to and including 7.6.3affected · semver
- 7.4.0 and later · up to and including 7.4.8affected · semver
- 7.2.0 and later · up to and including 7.2.11affected · semver
- 7.0.0 and later · up to and including 7.0.17affected · semver
Fortinet FortiProxy
- 7.6.0 and later · up to and including 7.6.3affected · semver
- 7.4.0 and later · up to and including 7.4.10affected · semver
- 7.2.0 and later · up to and including 7.2.14affected · semver
- 7.0.0 and later · up to and including 7.0.21affected · semver
Fortinet FortiSwitchManager
- 7.2.0 and later · up to and including 7.2.6affected · semver
- 7.0.0 and later · up to and including 7.0.5affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fortinet fortios7.0.0 and later · before 7.0.18
- fortinet fortios7.2.0 and later · before 7.2.12
- fortinet fortios7.4.0 and later · before 7.4.9
- fortinet fortios7.6.0 and later · before 7.6.4
Same product
fortinet: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-40684An authentication bypass using an alternate path or channel [CWE-288] in Fortinet FortiOS version 7.2.0 through 7.2.1 and 7.0.0 through 7.0.KEV99Now
- CVE-2018-13379An Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal") in Fortinet FortiOS 6.0.0 to 6.0.4, 5.6.3 to 5.6.7 and…KEV99Now
- CVE-2024-55591An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS version 7.0.0 through 7.0.16 and…KEV97Now
Published before and after this one in the same product
- ← EarlierCVE-2025-57740Oct 14, 2025 · An Heap-based Buffer Overflow vulnerability [CWE-122] in FortiOS version 7.6.2 and below, version 7.4.7 and below, version 7.2.10 and…35Monitor
- ← EarlierCVE-2025-54821Nov 18, 2025 · An Improper Privilege Management vulnerability [CWE-269] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through…24Monitor
- Later →CVE-2024-47570Dec 9, 2025 · An insertion of sensitive information into log file vulnerability [CWE-532] in FortiOS 7.4.0 through 7.4.3, 7.2.0 through 7.2.7, 7.0 all…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:6 | 2025-12-17 |
| Proof-of-concept repository on GitHub | stars:3 | 2025-12-27 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- CISA KEV+6 d
- First PoC+7 d
- TodayNov 14, 2026+340 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-25-0437 · Dec 10, 2025(Fortinet Çoklu Ürün Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.