Skip To Main Content
Eran Kinsbruner on Muck Rack

Eran Kinsbruner

Massachusetts
As seen in: Amazon Web Services, MSN, TechRadar, TechTarget, InfoWorld, InfoQ, DZone, Global Banking and Finance Review, Information Age, The New Stack and
VP Portfolio Marketing at Checkmarx ,speaker, author of amzn.to/2pTgTk8, lightrun.com #dev #AppSec #DevOps #DevSecOps #CISO #SAST #SCA #ASPM #DAST

Get in touch with Eran

Contact Eran, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Articles

There Is No Patch Tuesday on the Blockchain: Why Solidity Developers Need Fusion-Grade AppSec Before They Deploy

|
By Eran Kinsbruner
| checkmarx.com
For most software teams, security is a race against a clock. The median time from vulnerability disclosure to weaponization has collapsed from 840 days to 1.6 days, and 80% of exploitations now occur on or before the day of disclosure. That’s bad. But if you write Solidity, you already know your situation is categorically worse. A deployed Ethereum smart contract is immutable. It custodies value directly.
Open in Who Shared Issue with article?

Risk, Return, and Remediation: An Investment Strategy for Application Security

|
By Eran Kinsbruner
| checkmarx.com
Don’t Put All Your Code in One Basket. Every seasoned investor knows to never put your money behind a single asset. A successful investment strategy is diverse. No one puts all their money in stocks: markets correct. Real estate goes through cycles of boom and bust. Cash may feel safe, but inflation erodes its value over time. Having different investment assets helps offset volatility, so your portfolio as a whole stays resilient, even if that meme coin you bought on a whim takes a nosedive.
Open in Who Shared Issue with article?

Zombie CVEs: Put to Rest by Humans, Dug Back Up by AI Agents

|
By Eran Kinsbruner
| checkmarx.com
In 2023, a path traversal vulnerability in Starlette, one of Python’s most popular web frameworks  – was found, disclosed as CVE-2023-29159, and fixed. Case closed. The bug was dead and buried, like hundreds of thousands of CVEs before it: discovered by researchers, patched by maintainers, laid to rest by the security community’s accumulated, painstaking work. In 2026, a frontier AI coding agent rebuilt that same feature. The vulnerability walked right back out of the ground. And it wasn’t a one-off.
Open in Who Shared Issue with article?
See all 148 licensed articles (173 Total)