UNIVERSITY OF NICOSIA  |  IT

Cybersecurity Briefing

30 Oct 2026  ·  10 selected security developments

UNIC AI Learning Centre

ABOUT THIS BRIEFING

Prepared by the AI Learning Centre for UNIC IT, this weekly briefing monitors cybersecurity news, vulnerabilities, and security updates relevant to the University's technology environment. AI-powered analysis identifies and prioritises important developments, bringing together related reports and providing practical recommendations with links to original sources.

AI-assisted reporting. Please verify key details against the cited sources.

BRIEFING AT A GLANCE

10 selected security developments. Highest-priority items:

01 Patch exploited PHP2Shell flaws and assess additional PHP RCE  ·  Known exploited in the wild
Known exploitation and unauthenticated RCE make this the highest-priority remediation campaign for UNIC's inventoried PHP runtimes.
02 Update Node.js for exploited Brotli flaw and bundled security fixes  ·  Known exploited in the wild
This combines a known-exploited dependency with an actionable security update for UNIC's inventoried Node.js runtime.
03 Check Confluence edition for exploited Atlassian Data Center file exposure  ·  Known exploited in the wild
Known exploitation warrants a targeted Confluence edition check without incorrectly extending the advisory to Jira Cloud.

Development 01

Patch exploited PHP2Shell flaws and assess additional PHP RCE

Technologies: PHP (UNIC websites and internal systems)

●  Known exploited in the wild

CISA lists PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619 as known exploited, with unauthenticated remote code execution consequences. CERT-EU additionally reports CVE-2026-115560; exploitation evidence for the first two does not establish exploitation of this additional flaw, and UNIC's affected versions and configurations remain unverified.

Recommended action

Inventory PHP versions and handlers, prioritizing exposed services; for PHP2Shell, upgrade affected supported branches to at least 8.2.35, 8.3.36, 8.4.27 or 8.5.12, and separately verify the fix requirements for CVE-2026-115560. Where applicable, use the AWS WAF PHP managed rule group as interim defense while patching, and review upload and process activity for suspicious behavior.

CVEs: CVE-2026-109618, CVE-2026-109619, CVE-2026-115560

Sources

• PHP Memory Corruption Vulnerability · CISA KEV · 26 Oct 2026
• PHP Stale Internal Request-State Vulnerability · CISA KEV · 26 Oct 2026
• Critical Vulnerabilities in PHP · CERT-EU · 23 Oct 2026
• PHP web runtimes (CVE-2026-109618 and CVE-2026-109619) · AWS Bulletin · 21 Oct 2026
• Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities… · AWS Security Blog · 22 Oct 2026
• Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public… · AWS Security Blog · 21 Oct 2026

Development 02

Update Node.js for exploited Brotli flaw and bundled security fixes

Technologies: Node.js

●  Known exploited in the wild

Node.js security updates address Brotli decoder memory corruption with possible remote code execution, alongside DNS, TLS verification and other bundled-component issues. CISA confirms known exploitation of CVE-2026-111497 specifically; UNIC exposure depends on installed versions and processing of untrusted Brotli streams.

Recommended action

Check deployed runtimes and container images, upgrading affected Node.js branches to at least 22.23.4, 24.22.1 or 26.12.1 as appropriate. Restrict untrusted Brotli decompression until updated, and inspect separately bundled Brotli dependencies that a runtime upgrade might not replace.

CVEs: CVE-2026-105482, CVE-2026-105483, CVE-2026-106069 (+7 additional CVEs in linked advisories)

Sources

• Wednesday, October 21, 2026 Security Releases · Node.js · 21 Oct 2026
• Google Brotli Unchecked Return Value Vulnerability · CISA KEV · 27 Oct 2026
• A Vulnerability in Brotli Library Could Allow for Remote Code Execution · CIS / MS-ISAC · 28 Oct 2026

Development 03

Check Confluence edition for exploited Atlassian Data Center file exposure

Technologies: Atlassian Confluence

●  Known exploited in the wild

CISA lists an exploited arbitrary-file-access vulnerability affecting multiple self-managed Atlassian Data Center products, allowing unauthenticated access to specific files under the web root. UNIC's Confluence edition is unspecified; its inventoried Jira Cloud service is not the affected Jira Data Center product.

Recommended action

Establish whether Confluence or any separately deployed Atlassian systems use Data Center editions, then check versions and internet exposure. Apply vendor fixes or mitigations to affected self-managed installations; do not treat Jira Cloud as affected by this advisory.

CVEs: CVE-2026-21589

Sources: CISA KEV · 15 Oct 2026  ·  CIS / MS-ISAC · 12 Oct 2026

Development 04

Coordinate Next.js upgrades for conditional RCE, cache leakage and DoS

Technologies: Next.js

Next.js advisories cover possible RCE through SVG image optimization on glibc-based Linux, a separate unauthenticated RCE involving Cache Component functions returning multiple typed arrays, Server Actions DoS, and nested-cache content leakage. These are distinct vulnerabilities with different feature prerequisites; no in-the-wild exploitation is established in the supplied reporting.

Recommended action

Verify Next.js versions, image processing dependencies, App Router features and cache configuration; upgrade affected applications to 15.5.28 or 16.4.1 as appropriate, using 16.4.1 for affected version-16 Cache Component deployments. For the SVG issue, sharp 0.35.5 or later is a supported mitigation; it does not remediate the other vulnerabilities.

CVEs: CVE-2026-96889, CVE-2026-94482, CVE-2026-103004

Sources

• Next.js: Unauthenticated Remote Code Execution in Image Optimization API when… · GitHub · 22 Oct 2026
• Next.js: Unauthenticated Remote Code Execution in `use cache` functions… · GitHub · 22 Oct 2026
• Next.js: Denial of Service in App Router using Server Actions · GitHub · 22 Oct 2026
• next.js cache leak across root param values in nested 'use cache' functions · GitHub · 22 Oct 2026

Development 05

Apply cumulative GitLab security updates to affected self-managed instances

Technologies: GitLab

Consecutive GitLab CE/EE releases address multiple vulnerabilities, including distinct critical unauthenticated code-execution flaws in regular-expression compilation, CVE-2026-97229 and CVE-2026-110264. The supplied detection-rule and compromise-assessment guidance does not establish observed exploitation, and UNIC's hosting model is unknown.

Recommended action

Confirm whether UNIC operates self-managed GitLab and identify its branch and version. Upgrade affected installations to the appropriate cumulative release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13, following supported upgrade paths, and use available detection guidance to assess suspicious activity.

CVEs: CVE-2026-110264, CVE-2026-15723, CVE-2026-112212 (+11 additional CVEs in linked advisories)

Sources

• GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10,… · GitLab · 21 Oct 2026
• GitLab Critical Patch Release: 19.4.2, 19.3.5, 19.2.8 · GitLab · 12 Oct 2026
• Critical Vulnerability in GitLab Community and Enterprise Editions · CERT-EU · 22 Oct 2026

Development 06

Review certificate chains before AWS removes compromised CA trust

Technologies: AWS Application Load Balancer, Amazon CloudFront

AWS reports recoverable eMudhra/emSign intermediate CA keys caused by catastrophic entropy failures and is removing affected roots from service trust bundles. Relevant ALB authentication or CloudFront certificate-validation configurations could face trust-security risks or certificate-validation failures; UNIC's certificate chains and affected features are unverified.

Recommended action

Check whether ALB OIDC/JWT validation endpoints or CloudFront origins depend on affected emSign/eMudhra certificate chains. Replace dependent certificates where necessary and test authentication and origin connectivity as AWS trust-store changes take effect.

CVEs: CVE-2026-111943

Sources: AWS Bulletin · 25 Oct 2026

Development 07

Update Django for denial-of-service, request-forgery and privilege-abuse fixes

Technologies: Django

Django security releases address multiple issues including potential DoS, request forgery involving spatial lookup byte values, and model-formset privilege abuse. Django is inventoried at UNIC, but installed versions and use of the affected features are not established.

Recommended action

Identify deployed Django versions in applications, containers and virtual environments, and update affected supported branches to at least 6.1.2, 6.0.9 or 5.2.18. Where spatial lookup processing is relevant, review attacker-controlled raster inputs and the supplied GDALRaster and input-limiting mitigations.

CVEs: CVE-2026-77050, CVE-2026-84429, CVE-2026-87890 (+3 additional CVEs in linked advisories)

Sources: Django · 6 Oct 2026

Development 08

Review Vite development-server exposure and update editor dependencies

Technologies: Vite

Related Vite and launch-editor updates address development-server file access, limited four-byte disclosure, conditional cross-origin script execution, and editor command-injection paths. Applicability depends on network exposure, middleware configuration, operating system and editor behavior; these advisories do not establish vulnerabilities in production static builds.

Recommended action

Inventory Vite and launch-editor versions and restrict development servers to trusted access. Apply releases fixing each applicable advisory: the supplied fixes include Vite 8.3.3/8.2.4 for the four-byte disclosure and launch-editor 2.14.2 for CVE-2026-112944; separately verify the fixes and prerequisites for the other editor, middleware and file-access issues.

CVEs: CVE-2026-112946, CVE-2026-112947, CVE-2026-112944 (+3 additional CVEs in linked advisories)

Sources

• Vite: Files outside `server.fs.allow` could be served when project paths match… · GitHub · 21 Oct 2026
• Vite: First 4 bytes of files outside of `server.fs` setting is exposed by… · GitHub · 21 Oct 2026
• launch-editor: Editor CLI flag misinterpretation causing arbitrary command… · GitHub · 20 Oct 2026
• launch-editor: `fs.existsSync()` existence check can be bypassed on Windows · GitHub · 20 Oct 2026
• launch-editor: escapeCmdArgs() omits % escaping on Windows · GitHub · 20 Oct 2026
• Vite: Cross origin script execution through Vite custom middleware · GitHub · 21 Oct 2026

Development 09

Check PostgreSQL Anonymizer installations for critical masking-protection fixes

Technologies: PostgreSQL

PostgreSQL Anonymizer 3.3 fixes 12 vulnerabilities described as critical to the extension's privacy and masking protections. This is an extension-specific issue, not evidence of a PostgreSQL core vulnerability; UNIC's use of the extension is unconfirmed.

Recommended action

Check PostgreSQL extension inventories for Dalibo/PostgreSQL Anonymizer and record installed versions. If present and affected, upgrade to 3.3 and assess the vendor recommendation to change the anon.salt setting, validating the effects on masking workflows.

CVEs: CVE-2026-110181, CVE-2026-110182, CVE-2026-110183 (+9 additional CVEs in linked advisories)

Sources: PostgreSQL · 28 Oct 2026

Development 10

Verify Windows exposure to known-exploited shell command injection

●  Known exploited in the wild

CISA identifies CVE-2026-96951 as a known-exploited Microsoft Windows shell command-injection vulnerability. Although the preliminary assessment associates it with SQL Server, the more specific KEV description identifies Windows; neither Windows deployment nor affected versions at UNIC are established by the supplied inventory.

Recommended action

Check endpoint and server inventories for Windows systems, then determine applicability and update status against Microsoft guidance for CVE-2026-96951. Apply relevant Windows fixes where needed; do not classify SQL Server itself as vulnerable based on the preliminary product attribution.

CVEs: CVE-2026-96951

Sources: CISA KEV · 13 Oct 2026  ·  CIS / MS-ISAC · 13 Oct 2026

Inclusion highlights a potential security concern based on public reporting and UNIC's technology inventory. It does not confirm that UNIC runs an affected version or has been compromised.

Prepared by the AI Learning Centre (AILC) for UNIC IT.