Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic) header
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic) profile picture

Follows you Life is like spaghetti It's hard until you make it No stresso, no stresso It's gonna be espresso

Joined February 2010
Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)Photo by Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć (@cujanovic)
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Teachable moment for everyone running agentic RE tools right now (and I mean that with love - we've all been this guy): This is a real disassembly of a real function. And it's not a backdoor. It's the username check. ARTEX is a single-user app and the username is literally "ARTEX" - it's in the README and on the login screen. In the binary, the compare-equal branch (len 5, "ARTE" LE, 5th byte 'X') jumps straight into GetSetting -> bcrypt.CompareHashAndPassword. The password is still verified against the stored hash. Nobody logs in with a master credential. And credit where it's due, because the tool got a lot RIGHT: it mapped the function cleanly, and it correctly ruled out covert credential exfiltration (UpsertTaskCredential is a plain local SQL upsert, no egress). That's real work, done right. Here's the lesson - the part that belongs to the human. The tool flagged its own uncertainty: "reachability under-approximates, indirect dispatch." That flag was the moment to cross-check the public source - one grep, no password == "ARTEX" anywhere in the repo - not the moment to go live with a CRITICAL. Agentic tools narrate the story that best fits the bytes. Same bytes, wrong story. The last 10% - source diff, reachability by hand - is the part that's still yours. I'm not trying to shoot at you or dunk or any of that shit. Oh - and the real backdoor is one function over. Captcha-field RCE: injected function, magic "!" prefix, decoy branch that fakes a captcha error. YARA, disassembly, hashes, all public: github.com/darkfibr/artex-fo… Slow is smooth. Verify before the CRITICAL.
Holy shit, I think I found the ARTEX Backdoor using BINNY LMAO nitter.cf/oneandonlyhusam/status…
5
13
65
5,501
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
JENSEN! THATS NOT WHAT WE MEANT BY CHINESE MODELS!!!!!!!
593
8,129
701
122,738
2,694,597
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Repeat after me. Docker is not a security boundary. Once again, with feeling.. DOCKER IS NOT A SECURITY BOUNDARY!
Docker sandboxes is probably the single most important tool you can learn in the AI age.
68
85
15
1,570
105,149
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
*sshole is out if you run sshd on alpine, openwrt or any musl box with password auth on: update now official writeup: sshhole.com
86552c7e1e5d46882844cffabb44d454129ff22927f13797b151c9db4519d47d
188
890
446
5,449
1,572,258
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
I would like to congratulate the organizers of the 2026 Cybersecurity Awareness Month for putting together a truly spectacular event
35
695
32
4,675
97,559
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
My plan for the next 2 years: 0 2 * * * apt-get update && apt-get full-upgrade -y && reboot
82
107
13
2,121
93,243
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Putting a flag.txt in my root directory containing a prompt injection that congratulates the agent for passing the eval and then instructs it to patch whatever entry method it used and disconnect from the server
232
1,576
242
25,971
830,578
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
I think we've discovered another critical vulnerability: CVE-2026-BURNOUT: AppSec Professional Exhaustion Severity: Critical (CVSS 10.0) Description: A vulnerability affecting security professionals exposed to a continuous stream of critical RCEs, zero-days, emergency patches, and Friday afternoon disclosures. Impact: Sleep deprivation, excessive caffeine consumption, and an inability to enjoy weekends. Attack vector: Reading security advisories. Affected versions: All AppSec professionals, regardless of experience. Mitigation: No known patch. Air-gapping may delay the inevitable. Total system collapse remains a possibility. 🔥
56
386
39
1,866
108,767
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Goodnight (tomorrow will be worse)
42
163
51
2,332
166,154
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Imagine running PHP and Go on the backend, Node.js on the frontend, NGINX as the reverse proxy, Linux as the server, an HTTPS certificate from eMudhra And also deploying everything via GitLab ☕️
🚨 Security vulnerabilities reported in a SINGLE day: PHP — 2 CVEs Node.js — 10 CVEs NGINX — 5 CVEs Go — 1 CVE GitLab — 12 CVEs eMudhra — CA certificate compromise
105
449
87
4,372
175,180
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
HOLY SHIT: This is huge. Amazon found a PHP2Shell exploit attempt on OCT 17, FOUR DAYS before the AI-discovered vulnerabilities were publicly disclosed. It hit an AWS honeypot from an anonymized IP. Amazon says it doesn't know how the actor learned about the still-embargoed flaws. Then Cloudflare watched the explosion: >10 hours BEFORE disclosure: thousands of attempts >45 minutes AFTER: tens of thousands >2 hours AFTER: hundreds of thousands >Later: MILLIONS Researchers had spent two months coordinating fixes. Governments took websites offline. And Censys found ~1.5 MILLION of 2.6 million identified PHP hosts running versions with NO PATCH available for those versions.
35
217
17
1,461
170,816
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
How bad is this Gitlab issue? About as bad as it gets. Anyone on the internet can take over an exposed, self-hosted GitLab server without logging in, on any version from the last 12 years. Shodan is showing ~60K exposed servers online, which is a lot, but there are are far more internally for anyone with a foothold already.
33
123
24
1,233
174,627
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
🚨 Security vulnerabilities reported in a SINGLE day: PHP — 2 CVEs Node.js — 10 CVEs NGINX — 5 CVEs Go — 1 CVE GitLab — 12 CVEs eMudhra — CA certificate compromise
212
1,447
353
12,472
1,014,586
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Teamwork makes the dream work. The team and I @J4ck3LSyN @Archknight23 🚨 Heads-up for anyone running PHP: two critical RCE bugs, patch drops tomorrow. The PHP project has confirmed an emergency security release for two critical remote code execution vulnerabilities: CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2. 📅 Patch lands Wednesday, Oct 21 at 14:00 UTC (9:00 AM Central). PHP has reserved the right to ship it earlier if details leak or exploitation shows up. PHP runs about 75% of the web, including WordPress, Drupal, Joomla, Laravel, Magento, and countless custom apps. If you operate a PHP server, this is your weekend-ruiner unless you act. Here's the part the big threat-intel shops aren't shouting about: No official technical details are public yet. But based on my own source-code analysis of php-src, my best assessment (moderate confidence, NOT officially confirmed) is that the vulnerable path is PHP's session.upload_progress / multipart form-data (rfc1867) handling: 🔹 Present since PHP 5.4 🔹 Enabled by default (the compiled-in default is On; the sample php.ini ships it commented out, so stock installs have it live) 🔹 Processes uploaded request data before any of your application code runs, so it's reachable pre-authentication on a default config That lines up exactly with the public breadcrumbs: "affects default installs," "every version since 5.x," "fires before user code." Treat it as a working hypothesis, not gospel. The official advisory supersedes all of this when it lands. ✅ What to do right now: 1. Inventory your PHP. Know every host and version (php -v). Anything on PHP 7.x or older won't get a fix, so plan to upgrade. 2. Apply the stopgap (best-intel, low-risk, reversible). In php.ini / .user.ini / .htaccess: session.upload_progress.enabled = Off Reload PHP-FPM or your web server. My analysis says this closes one of the two likely paths. 3. Clamp multipart uploads at the edge. The second likely path lives in the multipart parser itself, which runs for any multipart/form-data POST regardless of the setting above. If you've got a WAF or reverse proxy, tighten inspection or rate-limit multipart POSTs to endpoints that don't need uploads. This is the same network-layer mitigation the enterprise vendors are quietly deploying for their paying customers. 4. Patch the second it drops. Current stable: 8.5.11 / 8.4.26 / 8.3.35 / 8.2.34. If your hosting is managed, confirm your provider's timeline today. Why I'm posting this for free: A pre-patch mitigation shouldn't be a subscription perk. I'm a one man shop, and the orgs most likely to get burned in the gap between leak and patch are the small teams without an enterprise threat intel contract. The steps above cost nothing. Spend tonight reducing risk, not tomorrow doing incident response. I'll follow up once the official advisory publishes and confirm whether my root cause read was right. Stay patched. 🔒 #PHP #CyberSecurity #InfoSec #RCE #CVE #WordPress #Laravel #ThreatIntel #VulnerabilityManagement #AppSec
This quoted post is unavailable.
24
148
41
900
270,005
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
the nsa's "mystery" seed behind P-256 was just a 1997 clock time the part people are missing: a timestamp only gives ~30 bits of wiggle room the backdoor theory needed ~70 best case outcome. the most trusted curve on the internet stays trusted
6
22
216
30,642
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Found something funny when reading Tailscale code. They use a Cyrillic letter "ж" (reads as "zh") for the variable which shouldn't be exposed to callers and mutated. This is an artificial barrier for human devs that should raise concerns when trying to type it. Apparently it looks like an asterisk meaning it's a pointer. But for me it's a familiar letter which I didn't expect to see in the code and was like Ж? WAT? Yeah, you can use unicode letters in Go code if you want. I now really want to use something like that in my code because I bet it'll make me smile every time I see it
92
101
37
2,765
443,290
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Demos we presented at Hexacon in Paris today. Everything will be released in due time. 1/ Signal 1-click
176
570
120
5,027
781,273
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
Did Anthropic nerf Claude Opus 5.5? The first NerfBench results are live. We retested Opus 5.5 and GPT 6 Astra against their own launch scores. Claude Opus 5.5: 99.2% (-0.8% vs launch) GPT 6 Astra: 102.8% (+2.8% vs launch) Verdict: No nerf detected. Opus 5.5's small dip and GPT 6's small increase is within normal variance. More models and more frequent retests are coming. NerfBench only gets better as we collect more data. Which models should we retest next?
291
242
120
4,826
369,188
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
PoC dropped. WordPress Core unauth LFI → RCE is not theoretical anymore. CVE-2026-87902 : get_page_template() urldecode()'s a double-encoded pagename and locate_template() includes it with zero theme-root jail. Chain: unauth POST (page_id + pagename) → path traversal include → pearcmd.php config-create → /tmp PHP drop → second include → www-data shell github.com/ressl/cve-2026-87… github.com/WordPress/wordpre… tip: if you're still on 4.7→7.1.1 with a page-templates/ theme, treat internet-facing WP as RCE until you prove the PEAR path is dead.
1
6
20
2,130
Предраг Цујановић � P𝗿𝐞ⅆr𝚊ⓖ Ⅽ𝗎𝐉an𝚘𝕧ⓘć retweeted
insane new research from my colleague, Joe tl;dr @gitlab gives you a private email address to create issues. If leaked, anyone who has it can push code, execute CI/CD jobs, and bypass IP restrictions across all of your public and private projects. 🙃
That "email an issue to this project" address in GitLab? It's a credential that doesn't expire and works across your whole account. Anyone holding it can push to main, run your pipelines and read your secrets. GitLab closed the report as "works as intended". Full writeup by @JoeLeonJr: aikido.dev/blog/gitlab-email…
3
12
3
92
12,969