Category Archives: news

News on main page.

Deep Document Sanitization: A New Approach to Security

CVE-2026-26110 [2] (in short: RCE in the Microsoft Office parser) is another warning sign: Microsoft has just patched a type confusion vulnerability in Microsoft Office, described as a vulnerability leading to remote code execution. In practice, it is another example showing that the problem is no longer limited to ?macros?, but includes a much broader attack surface in the document format itself and in Office parsers.

Treating macro signing as the main answer to document-related risk is now a very archaic approach. Macro and code signatures are, of course, still an important security control. But you have to ask whether a ?hacker? will not simply spend a few dollars on code signing.

Active or dangerous content can also hide in other parts of the file: external relationships, embedded objects, fields, templates, or unusual OOXML structures. That is why the time is coming for deep document sanitization: not just blocking macros, but disarming and reconstructing the entire file.

The nature of CVE-2026-26110 itself shows clearly that the ?document content? layer and Office parsers remain a real vector for code execution. It is no longer enough to teach users ?do not click links and unknown attachments?; we also have to teach that to Copilot (or other AI assistants).

I am impatiently waiting for someone to combine techniques from CVE-2026-0866 [1] (Zombie ZIP) with CVE-2026-26110. Yes, DOCX is a ZIP archive, and ZombieZip can make it unreadable for antivirus software, EDR, and other toys.

That is why deep document sanitization (Content Disarm & Reconstruction) increasingly seems like a sensible approach: analyzing and reconstructing a file instead of simply blocking macros.

Perhaps in many business processes it is worth returning to the question of whether we always need ?rich? formats. Sometimes a simpler format, and in some scenarios even good old RTF or other simplified ways of exchanging content, may be more reasonable for collecting data, CVs, or customer materials than the full, complex ecosystem of modern Office documents, Word files, and PowerPoint presentations.

Not because it is perfectly secure, but because reducing complexity very often reduces the attack surface as well.

…I am afraid I will come back to this topic again.

[1] https://isc.sans.edu/diary/rss/32786
[2] https://nvd.nist.gov/vuln/detail/CVE-2026-26110

So what if the camera is on the internet?

Sekurak [1] [ Polish portal providing substantive information on cyber security.] recently published an article about cameras at one of the railway stations being directly accessible from the internet. Comments such as ‘so what?’ quickly appeared under the post. At first glance, it may indeed seem that this is not a big deal – just an image from one camera.

The problem begins when we look at such data through the prism of today’s analytical capabilities. In the age of AI, image recognition and big data analysis, even a single video source can provide very valuable information: about the movement of people, behaviour patterns, meetings or logistics in a given place.

It is worth comparing this seemingly trivial situation with a recent report by The Telegraph, which stated: ‘Israel hacked Tehran’s traffic cameras to spy on Khamenei […] Israel hacked nearly all of Tehran’s traffic cameras to spy on Ali Khamenei before launching an attack to kill Iran’s supreme leader.’ This shows that camera infrastructure – especially when it covers public spaces – can have significance far beyond simple surveillance.

Even a single camera at a station, with audio enabled or not, can be a very valuable source of information. What is more, it is easy to be misled into thinking that such a device is only a passive sensor. In practice, however, an IP camera is nothing more than a small computer connected to a network.

This means that it often runs on an old, outdated operating system with a vulnerable web interface and many known security vulnerabilities. In such a scenario, the camera can become an entry point into the infrastructure, act as a jump host, enable network reconnaissance, and even lead to privilege escalation through vulnerabilities in the management interface (e.g., XSS or other classic web application errors).

In short, it is not just a camera. It is an element of IT infrastructure operating in a very sensitive location.

Additionally, I am willing to bet that the first thing the “administrator” of this camera did after receiving information that it was accessible from the Internet was to panic and log in from their workstation (with a million other tabs open, cached permissions, and perhaps even an administrative account). He logged into the unfortunate camera to check and “change the password”. If the editors of Sekurak could log into it, so could thousands of others. They might not have been so nice and could have modified its software and introduced malicious modifications to its code. Such devices should be treated as compromised and dangerous. Just as a doctor would treat a patient who came to a visit with bleeding tears and blisters on their skin.

And if we start to consider scenarios in which the compromise of such infrastructure could lead to real, kinetic effects in the physical world… that’s a topic for a separate post.

[1] https://www.linkedin.com/posts/michal-sajdak_kamera-z-jednego-z-polskich-dworc%C3%B3w-by%C5%82a-activity-7431610592974594048-2v82?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAEbrCYBiG9XAnLpx0DqmwqjjuBF1MrYIkE

[2] https://www.telegraph.co.uk/world-news/2026/03/03/israel-hacked-iranian-traffic-cameras-to-spy-on-khamenei/

odkurzacz iLife LINKI

https://github.com/kbickham/iLife_Robotic_Vaccum_v3s_Reverse_Engineer/blob/master/README.md

https://github.com/EliasKotlyar/IlifeX5Disassembly

https://github.com/ksya/ILIFERobot

https://github.com/ksya/ILIFERobot

http://roboforum.ru/forum90/topic16676.html

https://github.com/linvinus/open_ilife

https://github.com/Arduino-IRremote/Arduino-IRremote/issues/354

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjyqteKnOztAhUrpIsKHQ0fCVEQFjAGegQIFxAC&url=https%3A%2F%2Fdigikogu.taltech.ee%2Fen%2FDownload%2F6e438e93-2137-4a84-8134-2c50250c205b&usg=AOvVaw0DPS3RBY0EiHd_p3Omm-7W

Rubber Duck Debugging

Rubber duck debugging is an informal way of debugging code. The method involves a programmer, while trying to find bugs in code (code inspection), keeping a rubber duck or another inanimate object nearby. Line by line, the programmer explains to the duck or other object what each segment of code is supposed to do. During this review, bugs in the application should become apparent. The method is a version of the thinking-aloud method, a procedure recognized as an effective way to speed up problem solving.

https://pl.wikipedia.org/wiki/Metoda_gumowej_kaczuszki