How severe is CVE-2025-67718?

No CVSS score has been assigned to CVE-2025-67718 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-67718?

CVE-2025-67718 affects the following packages: formio (npm), formio (npm). Ecosystems affected: npm.

How do I fix CVE-2025-67718?

Update formio to 3.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67718 is resolved across your whole dependency graph.

How do I detect CVE-2025-67718 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for formio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-67718 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2025-67718 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-67718 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-67718?

CVE-2025-67718 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-67718?

CVE-2025-67718 is classified as CWE-178 (CWE-178), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-67718 published, and has it been updated?

CVE-2025-67718 was published on December 11, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-67718 — formio

Fix: formio/formio@1836bdd

CVE-2025-67718 is a CWE-178 vulnerability in formio. A fix is available for formio — see the affected versions and patch details below.

Formio improperly authorized permission elevation through specially crafted request path

Also known asGHSA-m654-769v-qjv7

Published

Dec 11, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67718.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

formionpm

4Kdownloads / week

Description

Security Advisory: Unauthorized permission elevation through specially crafted request path

Summary: A flaw in path handling could allow an attacker to access protected API endpoints by sending a crafted request path. This issue could result in unauthorized data disclosure under certain configurations.

Impact: In affected configurations, an unauthenticated or unauthorized request could retrieve data from endpoints that should be protected.

Affected versions: <= 3.5.6 <= 4.4.2

Fixed in: 3.5.7 4.4.3

Mitigation / Workarounds: Upgrade to 3.5.7 or later.

Disclosure timeline: Discovered 2025-05-22; fixed 2025-05-30; publicly disclosed 2025-12.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`formio`	all versions	3.5.7`npm install formio@3.5.7`
📦npm	`formio`	≥ 4.0.0-rc.1&&< 4.4.3	4.4.3`npm install formio@4.4.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for formio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update formio to 3.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67718 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

# Security Advisory: Unauthorized permission elevation through specially crafted request path **Summary:** A flaw in path handling could allow an attacker to access protected API endpoints by sending a crafted request path. This issue could result in unauthorized data disclosure under certain configurations. **Impact:** In affected configurations, an unauthenticated or unauthorized request could retrieve data from endpoints that should be protected. **Affected versions:** <= 3.5.6 <= 4.4.2 **Fixed in:** 3.5.7 4.4.3 **Mitigation / Workarounds:** Upgrade to 3.5.7 or later. **Disclosur

O3 Security · Impact-Aware SCA

Is CVE-2025-67718 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works