We're now accepting applications for our 2026 summer internship program!

Trail of Bits is hiring interns across our software assurance, security engineering, and research & development teams. Over the summer, you'll work on real projects that might include conducting security assessments for critical systems, developing open-source tools, and contributing research that advances the field.

Applications are open now through February! Learn more and apply here!
https://apply.workable.com/trailofbits/j/0C784B6D41/

cloudNative https://redd.it/1q5mjgj

@campuscodi

No, there's no major security vulnerability in zlib.

There's a stack buffer overflow in the contrib/untgz tool. However, these tools are unsupported as described by the README.contrib file: https://github.com/madler/zlib/blob/develop/contrib/README.contrib

"
All files under this contrib directory are UNSUPPORTED. They were
provided by users of zlib and were not tested by the authors of zlib.
Use at your own risk. Please contact the authors of the contributions
for help about these, not the zlib authors. Thanks.
"

#infosec #cybersecurity

[RSS] Ni8mare - Unauthenticated Remote Code Execution in n8n (CVE-2026-21858)

https://www.cyera.com/research-labs/ni8mare-unauthenticated-remote-code-execution-in-n8n-cve-2026-21858

[RSS] TrustZone Break-in Vulnerabilities in Ampere UEFI MM Drivers (Arbitrary Out-of-Bounds Write)

https://github.com/google/security-research/security/advisories/GHSA-jxxm-gxxf-64mg

[RSS] TrustZone Break-in Vulnerabilities in Ampere UEFI MM Drivers (Buffer Overflow and Stack Information Leak)

https://github.com/google/security-research/security/advisories/GHSA-46qj-g894-vrxr

[RSS] Breaking Down the Attack Surface of the Kenwood DNR1007XR - Part One

https://www.thezdi.com/blog/2026/1/6/breaking-down-the-attack-surface-of-the-kenwood-dnr1007xr-part-one

@cR0w @maaneeack @troed Don't take my word for it, I really didn't have time to dig in, but that's kind of the problem with slop isn't it?

@troed @maaneeack @cR0w The person who posted this also posted a bunch of other stuff in different projects. This is their "repro" for MongoDB:

```
./mdb_load -T /tmp/lmdb_asan < [crash_input_file]
```

...but I don't see `crash_input_file` anywhere. I smell slop.

(Source: https://seclists.org/fulldisclosure/2026/Jan/5 )

#jsPDF: Critical Path Traversal Vulnerability (CVE-2025-68428) in jsPDF - a widely-adopted #npm package for generating PDF documents in JavaScript applications allows attackers to read & exfiltrate arbitrary files from the local filesystem:
👇
https://www.endorlabs.com/learn/cve-2025-68428-critical-path-traversal-in-jspdf

An Act of Resistance

#webcomic #krita #miniFantasyTheater

@AlSweigart

...of course Phrack doesn't disappoint: https://github.com/xforcered/PhrackCTF/

@freddy will take a look thanks!

@joxean It doesn't have to be up-to-date, I'm going for samples, thanks!

Any recommendations for exploit dev focused #CTF with an archive of challenges?

I'm looking for samples and interested in code comprehension, less interested in obfuscation/VMs.

Edit: Native executables pls, not interested in polyglots, bytecode, etc. either.

I just registered for https://uasc.cc/ -- uASC (the Microarchitecture Security Conference) is on February 3rd, in Leuven, Belgium.

**Registration is free but mandatory!**

I would be happy to see all of you there :)

Especially from the Cologne and Ruhr area, it's just a train ride to Leuven -> join us!

"LLMs learn the same way a person does, it's not plagiarism"

This is a popular self-justification in the art-plagiarist community. It's frustrating to read because it's philosophically incoherent but making the philosophical argument is annoyingly difficult, particularly if your interlocutor maintains a deliberate ignorance about the humanities (which you already know they do). But there is a simpler mechanical argument you can make instead: "learning" is inherently mutual.

this is part of my aesthetic objection to LLMs -- they're just so profoundly inelegant. they represent a staggering amount of brute force in terms of time, information and material resources to solve problems that people *and computers* can address much more efficiently. they're a kind of anti-computing