CVE-2026-38057
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe iDirect iQ200 does not validate CSRF tokens on state-changing API endpoints after authentication. The /api/reboot endpoint accepts POST requests authenticated solely by a session cookie that lacks the SameSite attribute. A remote attacker can host a malicious web page that, when visited by an authenticated administrator, automatically submits a cross-site POST request causing an immediate device reboot and satellite link loss. Repeated attacks can sustain a denial-of-service condition.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe iDirect iQ200 fails to validate CSRF tokens on state-changing API endpoints, specifically the /api/reboot endpoint. Authentication relies solely on a session cookie missing the SameSite attribute, allowing cross-site request forgery. A remote attacker can embed malicious code in a webpage that, when visited by an authenticated administrator, silently triggers a POST request causing immediate device reboot and satellite link loss.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm iQ200 device is in useAccess the device web interface or check network inventory to identify the exact model (iDirect iQ200). Compare your device model against the affected product line.Affected if The device is an iDirect iQ200 unit
-
Identify session cookie configurationLog in to the device admin interface and inspect the HTTP response headers using browser developer tools or a command-line tool like curl -i after authenticating. Look for the session cookie in the Set-Cookie header and check if the SameSite attribute is present.Affected if The session cookie lacks the SameSite attribute or the SameSite attribute is not set to "Strict" or "Lax"
-
Test /api/reboot endpoint accessibilitySend a POST request to https://[device-ip]/api/reboot (or http if using HTTP) using curl or a similar tool while authenticated. Observe if the endpoint accepts the request without requiring a CSRF token.Affected if The /api/reboot endpoint accepts POST requests without validating a CSRF token
-
Verify administrative interface network exposureCheck the device network configuration to determine if the administrative web interface is accessible from outside trusted network segments. Review firewall rules or access control lists restricting access to port 443/80 on the device.Affected if The admin interface is accessible from untrusted or external networks without proper network segmentation
You are affected if you operate an iDirect iQ200 device where the session cookie lacks SameSite protection and the /api/reboot endpoint accepts requests without CSRF token validation, particularly if the admin interface is exposed beyond trusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patches when available. In the interim, implement network segmentation to restrict administrative access to trusted networks, and configure WAF/IPS rules to block cross-origin POST requests to /api/reboot from untrusted sources.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38057 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data