LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1364: JNC|IAQS and I6 - Missing Authentication

IAQS and I6 developed by JNC has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to directly operate system administrative functionalities.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-1364 is a critical missing-authentication flaw in JNC IAQS and I6. A remote attacker who is not logged in may be able to directly use administrative system functions. For organizations running these products, the business risk is loss of control over affected systems, with potential confidentiality, integrity, and availability impact.

Executive priority

Prioritize immediately if JNC IAQS or I6 is deployed, especially if reachable from the internet or partner networks. The vulnerability can allow unauthenticated administrative control. If the products are not present, document non-exposure and monitor vendor guidance.

Technical view

The CVE describes CWE-306 Missing Authentication affecting JNC IAQS and I6. CVSS 3.1 is 9.8, with network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high impact to confidentiality, integrity, and availability. Public sources do not provide affected version ranges beyond the sparse CVE data.

Likely exposure

Highest concern is any JNC IAQS or I6 administrative interface reachable from untrusted networks. The sources do not identify deployment models, default ports, version ranges, or whether internet-facing instances are common. Asset owners should verify whether either product is present and externally reachable.

Exploitation context

The CVE supports unauthenticated remote access to administrative functionality. The source bundle does not cite active exploitation, public exploit code, or CISA KEV listing. Treat as high urgency because exploitation requires no credentials or user interaction, but do not assume confirmed in-the-wild activity.

Researcher notes

Public details are limited. The CVE states missing authentication and administrative functionality exposure but does not include endpoints, affected version ranges, patches, or detection indicators. Avoid assumptions beyond IAQS and I6. Validation should focus on asset confirmation, reachable management interfaces, and vendor advisory follow-up.

Mitigation direction

  • Identify any JNC IAQS or I6 deployments in the environment.
  • Check JNC and TWCERT/CC advisories for product-specific updates or mitigations.
  • Restrict administrative access to trusted management networks only.
  • Block direct internet exposure where operationally possible.
  • Monitor logs for unauthenticated access to administrative functions.

Validation and detection

  • Confirm whether IAQS or I6 is installed or managed by third parties.
  • Document product versions and compare against vendor advisory details.
  • Review network exposure of administrative interfaces.
  • Check access controls for administrative functions.
  • Look for unusual configuration changes or administrative actions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1364 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-1364Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
JNCIAQS0unaffected
JNCI60unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.