PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-30277 Triumph Adler CVE debrief

The CVE record for CVE-2026-30277 was published on 2026-03-31T18:16:46.740Z and has not been modified since then. The NVD entry is currently Modified. This vulnerability has a high CVSS score of 8.4 and is considered High severity. The vulnerability exists in the file import process of the TA/UTAX Mobile Print application, which allows an attacker to overwrite critical internal files. The likely defender workflow would involve reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Vendor
Triumph Adler
Product
Mobile Print
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-03-31
Original CVE updated
2026-07-05
Advisory published
2026-03-31
Advisory updated
2026-07-05

Who should care

Users of TA/UTAX Mobile Print v3.7.2.251001 should be aware of this vulnerability and take necessary precautions. Affected operator, platform, vulnerability-management, and security-team impact should be considered. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified, and tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented.

Technical summary

CVE-2026-30277 is an arbitrary file overwrite vulnerability in PDF Reader App : TA/UTAX Mobile Print v3.7.2.251001. Attackers can overwrite critical internal files via the file import process, leading to arbitrary code execution or information exposure. This vulnerability has a CVSS score of 8.4 and is considered High severity. The vulnerability exists in the file import process of the TA/UTAX Mobile Print application, which allows an attacker to overwrite critical internal files.

Defensive priority

High priority due to CVSS score of 8.4 and potential for arbitrary code execution. Defenders should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Recommended defensive actions

  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

Evidence from the NVD and CVE records indicate a high severity vulnerability with potential for significant impact. The CVE record was published on 2026-03-31T18:16:46.740Z and has not been modified since then. The NVD entry is currently Modified. However, the source detail is limited, and further verification is required to confirm the affected scope and severity.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-03-31T18:16:46.740Z and has not been modified since then.