AI-written edition with a fictional anchor
Here is today's evening report. Sat, Oct 24, 18:17 HKT
18:06 HKT VeloCloud is under attack. Check the deployment and the version Arista’s advisory identifies the on-premises Orchestrator releases that need updating. Collabora’s separate fix applies to the built-in Nextcloud app, not standalone servers. read more
Kai Tanner, CYBER INTEL
AI-authored analysis · Fictional correspondent, real sourcesArista says CVE-2026-114625 is being actively exploited in VeloCloud Orchestrator. For an administrator deciding whether to interrupt a running system, the first question is which deployment and release the organisation has. Hosted services, including dedicated instances, have already been patched, according to Arista. [1]
The affected on-premises release trains are 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10, and 6.4.x before 6.4.2.12. Those three versions contain the fixes. Arista has not assessed releases that are out of support. VeloCloud Gateway and Edge are not affected by this flaw. [1]
An attacker needs access to the Orchestrator web interface and a valid session; even an Enterprise Read Only account is sufficient. Arista recommends upgrading, restricting administrative access while the fix is pending, and reviewing logs. If compromise is suspected, preserve the logs before remediation where feasible. [1]
Collabora’s separate CVE-2026-110447 affects the richdocumentscode built-in CODE Server app for Nextcloud before version 26.4.303. The vendor says to upgrade to that version or later, or remove the app. Disabling it is insufficient. The vulnerable path operates while the built-in server is not running; standalone Collabora Online servers are unaffected. Users on end-of-life Nextcloud versions 29 or earlier should upgrade Nextcloud or remove the app. [2]
These distinctions change the change ticket. A VeloCloud Edge appliance and a standalone Collabora server do not belong in the same queue as the affected deployments. Identify the exposed system, then attach the relevant fixed release and the investigation steps to its owner’s ticket.
Sources13:03 HKT Kyrie Irving scores 24 after Cooper Flagg exits with left shoulder soreness Dev Chatterjee has Dallas winning behind Kyrie Irving after Cooper Flagg left with shoulder soreness, with no return timetable established. read more
Dev Chatterjee, SPORTS
AI-authored analysis · Fictional correspondent, real sourcesCooper Flagg landed hard on his left shoulder and never returned after halftime. Aaron Nesmith had tried to block his shot from behind. Dallas spent the second half finishing a game its young forward could only leave unfinished.
The reported problem is left shoulder soreness. That establishes neither a more serious diagnosis nor a timetable for his return.
Kyrie Irving supplied 24 points as the Mavericks beat Indiana 121-105, spoiling Tyrese Haliburton’s home return. Haliburton got his welcome. Irving handled the eviction notice.
There is an expensive little irony underneath that rescue. In August, we wrote about a Dallas front office divided over Irving’s future after failing to trade him. On Friday, the player Dallas had failed to move helped carry the team after Flagg left with shoulder soreness. Keeping talent has uses that an offseason argument can overlook.
Dallas hosts San Antonio on October 25. That is the next game Flagg’s shoulder must let him play.
Continue reading
US Orders Diplomatic Departures After Warning of Iranian Attacks
The withdrawal of American personnel turns an official assessment of Iranian threats into a concrete reduction of the US diplomatic presence.
The United States has ordered departures from Saudi Arabia and is reducing staffing elsewhere in the region after officials said Iran was preparing attacks against Americans, The New York Times reports. The assessment has produced a concrete response: fewer American personnel will remain exposed. That is a consequential change in the diplomatic presence, even though the information supplied does not establish that the anticipated attacks have taken place. Washington is acting on a threat assessment before the threatened event.
The sequence matters. Officials identified preparations for attacks; Washington then moved to reduce its personnel. An ordered departure carries more institutional weight than a warning that leaves individuals to decide whether to travel. Here, the government is making the decision about its own presence. Diplomacy ordinarily depends on keeping people in place through uncomfortable circumstances. These departures show that the assessed danger has become serious enough for Washington to accept the costs of having fewer people there. The paperwork is diplomatic. The instruction is to leave.
Saudi Arabia is the named location for ordered departures, with staffing reductions elsewhere indicating a response extending beyond that country. But the report's description leaves important boundaries intact. It attributes the preparations to Iran through US officials; it does not supply independent confirmation in the material available here. Nor does a reduction in diplomatic staffing establish that a wider military confrontation has begun. The action is substantial on its own terms. It does not need an imagined next chapter to make it significant.
The result is a smaller American diplomatic presence because Washington judges the danger to Americans serious enough to move personnel. That decision cannot tell us whether an attack will happen. It does tell us that the threat has already changed how the United States operates in the region. The immediate consequence is therefore concrete: an official assessment has become a decision about who can safely remain.
All episodes and how to subscribe →