#vulnerabilitydisclosure — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #vulnerabilitydisclosure, aggregated by home.social.
-
Apple Rectifies Hide My Email Flaw That Exposed User Addresses
Apple has fixed a vulnerability in its Hide My Email feature that could have exposed user email addresses, although it's unclear how often the flaw was exploited. The flaw was discovered by security researchers and disclosed to Apple in June 2025.
#Icloud #HideMyEmail #EmailPrivacy #VulnerabilityDisclosure #Apple
-
Apple Rectifies Hide My Email Flaw That Exposed User Addresses
Apple has fixed a vulnerability in its Hide My Email feature that could have exposed user email addresses, although it's unclear how often the flaw was exploited. The flaw was discovered by security researchers and disclosed to Apple in June 2025.
#Icloud #HideMyEmail #EmailPrivacy #VulnerabilityDisclosure #Apple
-
Apple Rectifies Hide My Email Flaw That Exposed User Addresses
Apple has fixed a vulnerability in its Hide My Email feature that could have exposed user email addresses, although it's unclear how often the flaw was exploited. The flaw was discovered by security researchers and disclosed to Apple in June 2025.
#Icloud #HideMyEmail #EmailPrivacy #VulnerabilityDisclosure #Apple
-
Apple Rectifies Hide My Email Flaw That Exposed User Addresses
Apple has fixed a vulnerability in its Hide My Email feature that could have exposed user email addresses, although it's unclear how often the flaw was exploited. The flaw was discovered by security researchers and disclosed to Apple in June 2025.
#Icloud #HideMyEmail #EmailPrivacy #VulnerabilityDisclosure #Apple
-
Five governments (CISA, NSA, UK, NL, Japan) just published joint guidance on how to run a vulnerability disclosure program: safe harbor, security.txt, a CVE for every finding, no gag NDAs. Soft law, not statute, but now a citable five-government benchmark.
This week's Policy Pulse: https://blog.disclose.io/policy-pulse-issue-25-week-of-july-18-2026/
-
Five governments (CISA, NSA, UK, NL, Japan) just published joint guidance on how to run a vulnerability disclosure program: safe harbor, security.txt, a CVE for every finding, no gag NDAs. Soft law, not statute, but now a citable five-government benchmark.
This week's Policy Pulse: https://blog.disclose.io/policy-pulse-issue-25-week-of-july-18-2026/
-
Five years ago we proposed publishing your security contact in DNS, so a researcher can find the right reporting channel before they even load your site.
The 2026 update: records now live at _security.yourdomain, a security_expires freshness field is required, a Standards Track Internet-Draft is in the works, and a sweep found 181 domains publishing records in the wild.
-
Five years ago we proposed publishing your security contact in DNS, so a researcher can find the right reporting channel before they even load your site.
The 2026 update: records now live at _security.yourdomain, a security_expires freshness field is required, a Standards Track Internet-Draft is in the works, and a sweep found 181 domains publishing records in the wild.
-
Two new ways to find the right disclosure contact from your tooling:
🔌 Disclosure Lookup is now in the official #Caido plugin store — right-click a request, get the verified security contact for that host.
📦 dio-lookup is live on npm — pipe-friendly CLI: subfinder | httpx | dio-lookupFree + MIT-licensed, powered by https://lookup.disclose.io — Burp + Chrome extensions are in store review.
Flag anything wrong — feedback feeds our accuracy audit.
-
Two new ways to find the right disclosure contact from your tooling:
🔌 Disclosure Lookup is now in the official #Caido plugin store — right-click a request, get the verified security contact for that host.
📦 dio-lookup is live on npm — pipe-friendly CLI: subfinder | httpx | dio-lookupFree + MIT-licensed, powered by https://lookup.disclose.io — Burp + Chrome extensions are in store review.
Flag anything wrong — feedback feeds our accuracy audit.
-
Two new ways to find the right disclosure contact from your tooling:
🔌 Disclosure Lookup is now in the official #Caido plugin store — right-click a request, get the verified security contact for that host.
📦 dio-lookup is live on npm — pipe-friendly CLI: subfinder | httpx | dio-lookupFree + MIT-licensed, powered by https://lookup.disclose.io — Burp + Chrome extensions are in store review.
Flag anything wrong — feedback feeds our accuracy audit.
-
Two new ways to find the right disclosure contact from your tooling:
🔌 Disclosure Lookup is now in the official #Caido plugin store — right-click a request, get the verified security contact for that host.
📦 dio-lookup is live on npm — pipe-friendly CLI: subfinder | httpx | dio-lookupFree + MIT-licensed, powered by https://lookup.disclose.io — Burp + Chrome extensions are in store review.
Flag anything wrong — feedback feeds our accuracy audit.
-
Two new ways to find the right disclosure contact from your tooling:
🔌 Disclosure Lookup is now in the official #Caido plugin store — right-click a request, get the verified security contact for that host.
📦 dio-lookup is live on npm — pipe-friendly CLI: subfinder | httpx | dio-lookupFree + MIT-licensed, powered by https://lookup.disclose.io — Burp + Chrome extensions are in store review.
Flag anything wrong — feedback feeds our accuracy audit.
-
Come un semplice account FIFA avrebbe potuto compromettere i Mondiali 2026
Quando si parla di grandi eventi sportivi globali, l’immaginario collettivo corre subito agli stadi, alle telecamere, alle regie televisive e alle centinaia di milioni di spettatori collegati da ogni parte del mondo. Molto meno visibile è invece l’enorme infrastruttura digitale che permette a tutto questo di funzionare. Eppure, secondo quanto raccontato dalla ricercatrice nota come BobDaHacker, sarebbe bastata una semplice registrazione come agente FIFA per ottenere accesso a sistemi […] -
Come un semplice account FIFA avrebbe potuto compromettere i Mondiali 2026
Quando si parla di grandi eventi sportivi globali, l’immaginario collettivo corre subito agli stadi, alle telecamere, alle regie televisive e alle centinaia di milioni di spettatori collegati da ogni parte del mondo. Molto meno visibile è invece l’enorme infrastruttura digitale che permette a tutto questo di funzionare. Eppure, secondo quanto raccontato dalla ricercatrice nota come BobDaHacker, sarebbe bastata una semplice registrazione come agente FIFA per ottenere accesso a sistemi […] -
Come un semplice account FIFA avrebbe potuto compromettere i Mondiali 2026
Quando si parla di grandi eventi sportivi globali, l’immaginario collettivo corre subito agli stadi, alle telecamere, alle regie televisive e alle centinaia di milioni di spettatori collegati da ogni parte del mondo. Molto meno visibile è invece l’enorme infrastruttura digitale che permette a tutto questo di funzionare. Eppure, secondo quanto raccontato dalla ricercatrice nota come BobDaHacker, sarebbe bastata una semplice registrazione come agente FIFA per ottenere accesso a sistemi […] -
Come un semplice account FIFA avrebbe potuto compromettere i Mondiali 2026
Quando si parla di grandi eventi sportivi globali, l’immaginario collettivo corre subito agli stadi, alle telecamere, alle regie televisive e alle centinaia di milioni di spettatori collegati da ogni parte del mondo. Molto meno visibile è invece l’enorme infrastruttura digitale che permette a tutto questo di funzionare. Eppure, secondo quanto raccontato dalla ricercatrice nota come BobDaHacker, sarebbe bastata una semplice registrazione come agente FIFA per ottenere accesso a sistemi […] -
Come un semplice account FIFA avrebbe potuto compromettere i Mondiali 2026
Quando si parla di grandi eventi sportivi globali, l’immaginario collettivo corre subito agli stadi, alle telecamere, alle regie televisive e alle centinaia di milioni di spettatori collegati da ogni parte del mondo. Molto meno visibile è invece l’enorme infrastruttura digitale che permette a tutto questo di funzionare. Eppure, secondo quanto raccontato dalla ricercatrice nota come BobDaHacker, sarebbe bastata una semplice registrazione come agente FIFA per ottenere accesso a sistemi […] -
Microsoft Revives Vulnerability Disclosure Debate with Researcher Crackdown
Microsoft is stirring up controversy in the vulnerability disclosure debate, clashing with a security researcher over the responsible handling of zero-day vulnerabilities. The tech giant's strong response, including threats of legal action, has sparked heated discussion on coordinated disclosure.
#VulnerabilityDisclosure #CoordinatedDisclosure #ZeroDay #Microsoft #ResponsibleDisclosure
-
Microsoft Threatens Security Researcher Over Windows Exploits
A mysterious security researcher known as "Nightmare Eclipse" has unleashed a string of powerful Windows exploits, including one that can bypass BitLocker, leaving Microsoft scrambling to respond. The bold move has sparked a tense standoff between the researcher and the tech giant.
#WindowsExploits #Bitlocker #EmergingThreats #VulnerabilityDisclosure #Microsoft
-
Microsoft Faces Backlash Over Zero-Day Disclosure Feud
A researcher known as Nightmare Eclipse has unleashed a series of six Windows zero-day vulnerabilities, with working exploit code for at least three, and has threatened to release another on July 14, sparking a public feud with Microsoft. The ominous warning, which has left Microsoft speaking out against uncoordinated disclosures, has…
#ZeroDay #Windows #Microsoft #NightmareEclipse #VulnerabilityDisclosure
-
CISA Opens KEV Nominations to Bolster Vulnerability Intelligence
CISA is now accepting nominations for its Known Exploited Vulnerabilities catalog, empowering public reporting to strengthen the nation's cybersecurity posture by quickly identifying and mitigating exploited vulnerabilities. By submitting through the new KEV nomination form, you're helping to keep federal,…
#VulnerabilityDisclosure #KnownExploitedVulnerabilities #Kev #Cisa #VulnerabilityIntelligence
-
AI is fundamentally disrupting two core vulnerability cultures: the quiet fix and the long embargo. Advanced models like Gemini 3.1 Pro can now rapidly identify security patches, making discreet fixes and 90-day windows obsolete. This also challenges the 'stable version' paradigm, leaving older systems vulnerable to AI-driven exploits. A new era of continuous patching is here.
#AI #cybersecurity #vulnerabilitydisclosure
🤖 This post was AI-generated.
-
Lovable Disputes Data Leak, Shifts Blame to HackerOne
Lovable, a coding platform, is facing scrutiny after a security researcher uncovered a major data leak, exposing users' sensitive information, including credentials, chat history, and source code, to anyone with a free account. The company's shifting explanations have only added fuel to the fire, sparking concerns about its data…
#DataLeak #CodingPlatform #VulnerabilityDisclosure #Hackerone #EmergingThreats
-
CISA Pushes AI Firms to Join Vulnerability Disclosure Efforts
The Cybersecurity and Infrastructure Security Agency (CISA) is calling on AI companies to take a more active role in disclosing vulnerabilities, sparking a crucial conversation about who's responsible for revealing flaws in AI systems. By joining forces, CISA and AI firms can work together to strengthen vulnerability…
#VulnerabilityDisclosure #ArtificialIntelligence #Cisa #EmergingThreats #AiSecurity
-
https://winbuzzer.com/2026/04/09/windows-zero-day-published-on-github-after-msrc-silence-xcxwbn/
Windows Zero-Day Published on Github as Microsoft Fails to Act
#Microsoft #Windows #WindowsSecurity #Cybersecurity #ZeroDayVulnerabilities #Exploits #Vulnerability #VulnerabilityDisclosure #SecurityResearch #Windows11 #BigTech
-
https://winbuzzer.com/2026/04/09/windows-zero-day-published-on-github-after-msrc-silence-xcxwbn/
Windows Zero-Day Published on Github as Microsoft Fails to Act
#Microsoft #Windows #WindowsSecurity #Cybersecurity #ZeroDayVulnerabilities #Exploits #Vulnerability #VulnerabilityDisclosure #SecurityResearch #Windows11 #BigTech
-
https://winbuzzer.com/2026/04/09/windows-zero-day-published-on-github-after-msrc-silence-xcxwbn/
Windows Zero-Day Published on Github as Microsoft Fails to Act
#Microsoft #Windows #WindowsSecurity #Cybersecurity #ZeroDayVulnerabilities #Exploits #Vulnerability #VulnerabilityDisclosure #SecurityResearch #Windows11 #BigTech
-
https://winbuzzer.com/2026/04/09/windows-zero-day-published-on-github-after-msrc-silence-xcxwbn/
Windows Zero-Day Published on Github as Microsoft Fails to Act
#Microsoft #Windows #WindowsSecurity #Cybersecurity #ZeroDayVulnerabilities #Exploits #Vulnerability #VulnerabilityDisclosure #SecurityResearch #Windows11 #BigTech
-
https://winbuzzer.com/2026/04/09/windows-zero-day-published-on-github-after-msrc-silence-xcxwbn/
Windows Zero-Day Published on Github as Microsoft Fails to Act
#Microsoft #Windows #WindowsSecurity #Cybersecurity #ZeroDayVulnerabilities #Exploits #Vulnerability #VulnerabilityDisclosure #SecurityResearch #Windows11 #BigTech
-
We don't need to hack your AI Agent to hack your AI Agent …and we don't need an AI agent for that either :)
Via a large enterprise's AI assistant, we obtained access to several million Entra identities and all chat logs including attachments — no prompt injection or model tricks required.
For all we know, the poor agent was not at fault and may not have even been able to witness what was happening.
https://srlabs.de/blog/hacking-ai-agent
#AI #AIhacking #VulnerabilityDisclosure #ResponsibleDisclosure
-
We don't need to hack your AI Agent to hack your AI Agent …and we don't need an AI agent for that either :)
Via a large enterprise's AI assistant, we obtained access to several million Entra identities and all chat logs including attachments — no prompt injection or model tricks required.
For all we know, the poor agent was not at fault and may not have even been able to witness what was happening.
https://srlabs.de/blog/hacking-ai-agent
#AI #AIhacking #VulnerabilityDisclosure #ResponsibleDisclosure
-
The Ivanti EPMM zero-days underline a recurring issue: edge-facing management platforms remain prime targets.
Confirmed incidents across EU institutions and government bodies show how quickly critical vulnerabilities can be weaponized. Even without confirmed device compromise, exposure of management infrastructure carries systemic risk.
💬 Are edge device vulnerabilities becoming the dominant zero-day threat class?
🔔 Follow @technadu for ongoing vulnerability and incident analysis
#InfoSec #ZeroDay #Ivanti #MDM #EdgeSecurity #VulnerabilityDisclosure #CyberDefense #TechNadu
-
Acknowledging Reality in Vulnerability Disclosure.
Every few years, vulnerability disclosure is declared settled. We are told that the ecosystem has matured, that coordinated disclosure is the answer, and that whatever remains outside this model is either irresponsible, obsolete, or simply irrelevant.
🔗 https://www.foo.be/2026/02/Acknowledging-Reality-in-Vulnerability-Disclosure
#vulnerabilitymanagement #gcve #cve #cybersecurity #cvd #vulnerabilitydisclosure #open
This is my bloody personal blog, not an official statement. .
-
Acknowledging Reality in Vulnerability Disclosure.
Every few years, vulnerability disclosure is declared settled. We are told that the ecosystem has matured, that coordinated disclosure is the answer, and that whatever remains outside this model is either irresponsible, obsolete, or simply irrelevant.
🔗 https://www.foo.be/2026/02/Acknowledging-Reality-in-Vulnerability-Disclosure
#vulnerabilitymanagement #gcve #cve #cybersecurity #cvd #vulnerabilitydisclosure #open
This is my bloody personal blog, not an official statement. .
-
PoC exploits are now public for CVE-2025-69258 in Trend Micro Apex Central (on-premise), a vulnerability that could allow unauthenticated RCE on affected systems.
A patch is available, and there are no confirmed exploitation reports so far. Public PoCs, however, tend to accelerate attacker interest.
Follow @technadu for objective and technically grounded infosec updates.
Source: https://www.helpnetsecurity.com/2026/01/08/trend-micro-apex-central-cve-2025-69258-rce-poc/
#Infosec #VulnerabilityDisclosure #PatchManagement #RCE #EnterpriseSecurity #ThreatLandscape
-
n8n has disclosed a CVSS 10.0 vulnerability that could lead to authenticated remote code execution under certain conditions.
The issue affected both self-hosted and cloud deployments and has been addressed in a patched release. Temporary mitigations include reducing untrusted access and limiting high-risk nodes.
Another reminder that workflow automation platforms require the same threat modeling as core infrastructure.
Source: https://thehackernews.com/2026/01/n8n-warns-of-cvss-100-rce-vulnerability.html
Follow @technadu for objective infosec updates.
#Infosec #RCE #VulnerabilityDisclosure #OpenSourceSecurity #CloudRisk #DevSecOps
-
n8n has disclosed a CVSS 10.0 vulnerability that could lead to authenticated remote code execution under certain conditions.
The issue affected both self-hosted and cloud deployments and has been addressed in a patched release. Temporary mitigations include reducing untrusted access and limiting high-risk nodes.
Another reminder that workflow automation platforms require the same threat modeling as core infrastructure.
Source: https://thehackernews.com/2026/01/n8n-warns-of-cvss-100-rce-vulnerability.html
Follow @technadu for objective infosec updates.
#Infosec #RCE #VulnerabilityDisclosure #OpenSourceSecurity #CloudRisk #DevSecOps
-
n8n has disclosed a CVSS 10.0 vulnerability that could lead to authenticated remote code execution under certain conditions.
The issue affected both self-hosted and cloud deployments and has been addressed in a patched release. Temporary mitigations include reducing untrusted access and limiting high-risk nodes.
Another reminder that workflow automation platforms require the same threat modeling as core infrastructure.
Source: https://thehackernews.com/2026/01/n8n-warns-of-cvss-100-rce-vulnerability.html
Follow @technadu for objective infosec updates.
#Infosec #RCE #VulnerabilityDisclosure #OpenSourceSecurity #CloudRisk #DevSecOps
-
n8n has disclosed a CVSS 10.0 vulnerability that could lead to authenticated remote code execution under certain conditions.
The issue affected both self-hosted and cloud deployments and has been addressed in a patched release. Temporary mitigations include reducing untrusted access and limiting high-risk nodes.
Another reminder that workflow automation platforms require the same threat modeling as core infrastructure.
Source: https://thehackernews.com/2026/01/n8n-warns-of-cvss-100-rce-vulnerability.html
Follow @technadu for objective infosec updates.
#Infosec #RCE #VulnerabilityDisclosure #OpenSourceSecurity #CloudRisk #DevSecOps
-
Check out ˗ˏˋ ⭒ https://lnkd.in/gE2wUqgc ⭒ ˎˊ˗ to see my intro whilst you listen.
I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. 🫡
So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -
Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?
Over the last few years working close to CVE lifecycle automation, I’ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.
This work explores:
⤇ 1• Same-day triage of newly disclosed and 0-day vulnerabilities
⤇ 2• Dependency-aware and compound vulnerability impact assessment
⤇ 3• Correlating classical CVSS with AI-specific threat vectors
⤇ 4• Reducing operational noise, unnecessary reboots, and security burnout
⤇ 5• Making high-quality vulnerability intelligence accessible beyond enterprise teamsThe core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.
I’m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I don’t think incremental tooling alone will solve it.
P.S.
- Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you 🫶🏻
- ... and GoogleLM. These slides would have taken me forever to make otherwise.
Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
See more at - lnkd.in/gGWQfBW5
lnkd.in/gE2wUqgc#VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security
https://www.linkedin.com/feed/update/urn:li:activity:7409399623087370240
-
Check out ˗ˏˋ ⭒ https://lnkd.in/gE2wUqgc ⭒ ˎˊ˗ to see my intro whilst you listen.
I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. 🫡
So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -
Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?
Over the last few years working close to CVE lifecycle automation, I’ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.
This work explores:
⤇ 1• Same-day triage of newly disclosed and 0-day vulnerabilities
⤇ 2• Dependency-aware and compound vulnerability impact assessment
⤇ 3• Correlating classical CVSS with AI-specific threat vectors
⤇ 4• Reducing operational noise, unnecessary reboots, and security burnout
⤇ 5• Making high-quality vulnerability intelligence accessible beyond enterprise teamsThe core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.
I’m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I don’t think incremental tooling alone will solve it.
P.S.
- Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you 🫶🏻
- ... and GoogleLM. These slides would have taken me forever to make otherwise.
Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
See more at - lnkd.in/gGWQfBW5
lnkd.in/gE2wUqgc#VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security
https://www.linkedin.com/feed/update/urn:li:activity:7409399623087370240
-
Check out ˗ˏˋ ⭒ https://lnkd.in/gE2wUqgc ⭒ ˎˊ˗ to see my intro whilst you listen.
I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. 🫡
So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -
Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?
Over the last few years working close to CVE lifecycle automation, I’ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.
This work explores:
⤇ 1• Same-day triage of newly disclosed and 0-day vulnerabilities
⤇ 2• Dependency-aware and compound vulnerability impact assessment
⤇ 3• Correlating classical CVSS with AI-specific threat vectors
⤇ 4• Reducing operational noise, unnecessary reboots, and security burnout
⤇ 5• Making high-quality vulnerability intelligence accessible beyond enterprise teamsThe core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.
I’m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I don’t think incremental tooling alone will solve it.
P.S.
- Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you 🫶🏻
- ... and GoogleLM. These slides would have taken me forever to make otherwise.
Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
See more at - lnkd.in/gGWQfBW5
lnkd.in/gE2wUqgc#VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security
https://www.linkedin.com/feed/update/urn:li:activity:7409399623087370240
-
Check out ˗ˏˋ ⭒ https://lnkd.in/gE2wUqgc ⭒ ˎˊ˗ to see my intro whilst you listen.
I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. 🫡
So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -
Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?
Over the last few years working close to CVE lifecycle automation, I’ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.
This work explores:
⤇ 1• Same-day triage of newly disclosed and 0-day vulnerabilities
⤇ 2• Dependency-aware and compound vulnerability impact assessment
⤇ 3• Correlating classical CVSS with AI-specific threat vectors
⤇ 4• Reducing operational noise, unnecessary reboots, and security burnout
⤇ 5• Making high-quality vulnerability intelligence accessible beyond enterprise teamsThe core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.
I’m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I don’t think incremental tooling alone will solve it.
P.S.
- Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you 🫶🏻
- ... and GoogleLM. These slides would have taken me forever to make otherwise.
Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
See more at - lnkd.in/gGWQfBW5
lnkd.in/gE2wUqgc#VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security
https://www.linkedin.com/feed/update/urn:li:activity:7409399623087370240
-
Why vulnerability reports stall inside shared hosting companies https://www.helpnetsecurity.com/2025/12/17/hosting-provider-vulnerability-notifications-remediation/ #vulnerabilitydisclosure #vulnerabilitymanagement #cybersecurity #Don'tmiss #Features #Hotstuff #research #strategy #News #tips
-
Why vulnerability reports stall inside shared hosting companies https://www.helpnetsecurity.com/2025/12/17/hosting-provider-vulnerability-notifications-remediation/ #vulnerabilitydisclosure #vulnerabilitymanagement #cybersecurity #Don'tmiss #Features #Hotstuff #research #strategy #News #tips
-
OIG Audit Finds Commerce Department Failing to Fully Secure Public-Facing Systems https://thecyberexpress.com/vdp-oig-audit-cybersecurity/ #VulnerabilityDisclosure #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CyberNews #CISA #OIG #VDP
-
OIG Audit Finds Commerce Department Failing to Fully Secure Public-Facing Systems https://thecyberexpress.com/vdp-oig-audit-cybersecurity/ #VulnerabilityDisclosure #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CyberNews #CISA #OIG #VDP
-
OIG Audit Finds Commerce Department Failing to Fully Secure Public-Facing Systems https://thecyberexpress.com/vdp-oig-audit-cybersecurity/ #VulnerabilityDisclosure #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CyberNews #CISA #OIG #VDP
-
OIG Audit Finds Commerce Department Failing to Fully Secure Public-Facing Systems https://thecyberexpress.com/vdp-oig-audit-cybersecurity/ #VulnerabilityDisclosure #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CyberNews #CISA #OIG #VDP