CVE-2026-38059
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 exposes the /api/identity and /api/ REST API endpoints without authentication. An unauthenticated attacker with network access can retrieve sensitive device information including the serial number, Device ID (DID), Terminal Private Key identifier (TPK), MAC address, and exact firmware version. The DID and TPK are used for satellite network authentication in the iDirect platform, potentially enabling terminal impersonation and network reconnaissance.
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 satellite terminal exposes /api/identity and /api/ REST API endpoints without any authentication required. An unauthenticated attacker with network access can retrieve sensitive device identifiers including Device ID (DID), Terminal Private Key identifier (TPK), serial number, MAC address, and firmware version. These credentials are used for authentication in iDirect's satellite network platform, enabling potential terminal impersonation and network reconnaissance.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 terminal presenceIdentify the device on your network by checking for iDirect iQ200 signatures via network scanning, device enumeration, or by inspecting HTTP headers and responses from the device's web interface.Affected if The device is an iDirect iQ200 satellite terminal on your network.
-
Check if /api/identity endpoint is accessibleSend an HTTP GET request to http://<device_ip>/api/identity without providing any authentication credentials or headers.Affected if The endpoint returns a 200 OK response with device identifiers (DID, TPK, serial number, MAC, firmware) without requiring authentication.
-
Check if /api/ endpoint is accessibleSend an HTTP GET request to http://<device_ip>/api/ without providing any authentication credentials or headers.Affected if The endpoint returns a 200 OK response or exposes API functionality without requiring authentication.
-
Verify sensitive data exposureInspect the response body from the unauthenticated API calls for the presence of Device ID (DID), Terminal Private Key identifier (TPK), serial number, MAC address, and firmware version fields.Affected if The API responses contain any of these sensitive identifiers without authentication.
A user is affected if they have an iDirect iQ200 terminal where the /api/identity or /api/ endpoints are reachable and return sensitive device information without requiring any authentication credentials.
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 dataImplement authentication on the exposed REST API endpoints, or restrict network access via firewall/segmentation to prevent unauthorized access to these endpoints. Apply vendor firmware updates when available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38059 — 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-38059 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