CVE-2026-22876VulnerabilityPublished 16 Jan 2026

CVE-2026-22876: TOA Multiple Network Cameras TRIFORA 3 series · Path Traversal

Affects TOA Multiple Network Cameras TRIFORA 3 seriesSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
TOA CorporationMultiple Network Cameras TRIFORA 3 series	Affected =see the information provided by the vendor	Fixed in–

AI-suggested

1. Apply vendor-provided patches or firmware updates as soon as they become available to remediate the path traversal vulnerability. 2. Restrict and audit monitoring user privileges rigorously, ensuring that only trusted personnel have access to low-level accounts on the cameras. 3. Implement network segmentation to isolate network cameras from critical systems and limit access to the camera management interfaces to trusted networks or VPNs. 4. Employ strong authentication mechanisms for camera access, including multi-factor authentication where supported. 5. Monitor access logs for unusual or unauthorized file retrieval attempts from the cameras. 6. Regularly review and update device configurations to minimize exposed services and unnecessary permissions. 7. Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts targeting path traversal vulnerabilities. 8. Educate security and IT teams about this vulnerability to ensure rapid response and mitigation.

Description

Path Traversal vulnerability exists in multiple Network Cameras TRIFORA 3 series provided by TOA Corporation. If this vulnerability is exploited, arbitrary files on the affected product may be retrieved by a logged-in user with the low("monitoring user") or higher privilege.

Impact

For European organizations, this vulnerability poses a confidentiality risk by allowing unauthorized access to arbitrary files on network cameras, potentially exposing sensitive surveillance data, configuration details, or credentials stored on the device. This could facilitate further lateral movement or targeted attacks within the network. Organizations in sectors such as critical infrastructure, government, transportation, and large enterprises that deploy TOA Corporation’s TRIFORA 3 series cameras for security monitoring are at heightened risk. The exposure of sensitive files could lead to privacy violations, regulatory non-compliance (e.g., GDPR), and reputational damage. Since the vulnerability requires only low-level monitoring privileges, attackers who compromise or misuse such accounts can exploit this flaw. The lack of impact on integrity and availability limits the risk of disruption but does not diminish the importance of protecting confidentiality. The medium severity score suggests a moderate but actionable risk that should be addressed promptly to prevent potential data leaks and escalation of attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jan 2026, 08:42 UTC

Technical details

References

Community reviews

Related threats