CVE-2026-1364
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 · uneditedIAQS and I6 developed by JNC has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to directly operate system administrative functionalities.
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 · moderate confidenceIAQS and I6 by JNC contain a missing authentication vulnerability that allows unauthenticated remote attackers to directly access and operate system administrative functionalities. This critical flaw bypasses all authentication mechanisms, granting full administrative control to anyone who can send requests to the affected system.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify if JNC IAQS or I6 is installedCheck system inventory, installed software list, or product documentation for presence of JNC IAQS or I6. Look for service processes named 'iaqs', 'i6', or 'jnc' running on the system.Affected if JNC IAQS or I6 software is found installed on the system
-
Locate administrative interface endpointsReview application configuration files, documentation, or network scans to identify administrative URLs or ports. Common paths may include /admin, /management, /api/admin, or similar privileged endpoints.Affected if Administrative interface endpoints are exposed or accessible
-
Test if authentication is required for admin accessSend an HTTP request to identified administrative endpoints without providing any credentials, session tokens, or authentication headers. Observe if the system returns administrative functionality or allows privileged operations.Affected if Administrative functions are accessible without any authentication credentials
-
Verify authentication enforcement on privileged operationsAttempt to perform privileged administrative actions (such as configuration changes, user management, or system modifications) without authenticating. Check if the system returns success or allows the operation.Affected if Privileged operations execute successfully without authentication validation
A system is affected if JNC IAQS or I6 is installed and administrative endpoints or privileged operations are accessible without 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 robust authentication and authorization controls for all administrative endpoints and functionalities. Restrict access to administrative interfaces to authorized users only, and validate session tokens on every privileged operation.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1364 — 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-1364 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