Spotted something the IT security community should know about — a fresh CVE, a vendor advisory, an urgent patch, a malware campaign or an observation from your day job? Submit your story via the form below — free of charge and without an account.

1. Submit — category, headline, text and a source link into the form, hit send.
2. Editorial review — the editors promptly check your submission against the community rules.
3. Publication — approved stories appear in the news feed, on the homepage and in the topic channels — with author attribution and a link to your website if you like.

A good fit is anything with a genuine security angle: vulnerabilities, patches, warnings, campaigns, research. For in-depth multi-paragraph technical articles, please use submit a guest article instead.

By submitting, you make tsecurity.de a better source for everyone — thank you! To keep the feed trustworthy, we all stick to these rules:

1. Provide evidence — cite the source (URL, vendor advisory, CVE ID or repository). Submissions without verifiable origin are retracted.
2. Separate facts from opinion — context and judgement are welcome, as long as they are labelled.
3. No personal data of third parties — neither in the submission nor in the source (no doxxing, no leaked customer data).
4. Responsible disclosure — name affected products and mitigations; leave out exploitable code.
5. No advertising — product news only with a genuine security angle, not as ad copy.
6. Respect copyright — quote briefly with attribution instead of copying entire articles.

Editors review submissions promptly; feedback is welcome via the contact routes in the imprint. Legal frame: terms section 4a and the privacy policy.