Latest News:<\/strong> 2026-07-24 Update: The public intrusion test on e-voting this year has ended. We want to thank everyone, who participated!<\/p>\n 2026-07-06 Update: The public intrusion test has once again started and will run until the 24th July. Good luck!<\/p>\n 2026-06-08 Update: The wait is almost over! The Public Intrusion Test (PIT) will return on 06 July 2026<\/strong>, featuring a special highlight: the PIT+ private program<\/strong>. For the first time, we will deploy the PIT environment with adjusted security measures<\/strong>, allowing you to test its robustness in an extended setup beyond the usual constraints. If you are interested in participating in the PIT+ program, please contact us at evoting@post.ch<\/a>. Please note that the number of available slots is limited<\/strong>. If you are unable to secure a spot this year, you will have another opportunity next time.<\/p>\n 2026-02-24 Update: We've updated our reporting requirements (see below). Check them out to keep you reports valid!<\/p>\n 2025-08-25 Update: The public intrusion test on e-voting this year has ended. We want to thank everyone, who participated!<\/p>\n 2025-07-28 Seize the opportunity<\/strong>: The public intrusion test has once again started and will run until the 24th August. Explore and directly test the live infrastructure through the web interface. Details can be found in \u201cC.4 Web application & infrastructure\u201d<\/p>\n 2025-05-16 Update: A new scope has been added to the program: the E-Voting Voting Print Service Source code<\/strong>! You can find the code here<\/a><\/p>\n 2024-07-04 Update: The public intrusion test on e-voting this year has ended. We want to thank everyone, who participated!<\/p>\n 2024-06-12 Seize the opportunity<\/strong>: The public intrusion test has once again started and will run until the 3th July. Explore and directly test the live infrastructure through the web interface. Details can be found in \u201cC.4 Web application & infrastructure\u201d Also, don\u2019t miss out our new bounty grid, which increased and is active starting today. <\/strong><\/p>\n 2024-02-22 Update: We published a new major release of our e-voting system. Take a look at our repository<\/a>!\"<\/p>\n 2023-07-31 Update: The public penetration test on e-voting this year has ended. We want to thank everyone, who participated!<\/p>\n 2023-07-08 Don\u2019t miss out:<\/strong> The public penetration test on e-voting will run until 31 July on \"pit.evoting.ch\"<\/a>. The scope is detailed below under \u201cC.4 Web application & infrastructure (intrusion test)\u201d Take your chance to check out and test the live infastructure directly through the webinterface!<\/p>\n 2023-05-25 Update: We published a new release with new source code components<\/strong> and actualized our E2E environment. Take a look at our repository<\/a> and stay up to date by signing up for our [infomail] 2022-12-16 Update: We published a new release and actualized our E2E environment. Take a look at our repository<\/a> and stay up to date by signing up for our infomail<\/a>.<\/p>\n This bug bounty programme is a permanent and public programme that is a dedicated part of the Swiss Post e-voting community programme (hereinafter ECP): https:\/\/swisspost-digital.ch\/evoting-community<\/a> <\/p>\n The goal of this programme is to continuously improve the security of the Swiss Post e-voting system. <\/p>\n By participating for the ECP public bug bounty, you agree to comply with this Policy and with the Code of Conduct for the ECP (hereinafter CoC). In case of conflict between this Policy and the CoC, the Policy has priority. If you do not accept this policy and the CoC, please do not participate in the ECP public bug bounty.<\/p>\n Please read carefully the programme policy, especially the indications regarding the different scopes of this programme and the corresponding reporting requirements<\/strong>. Please also follow our Code of Conduct<\/a><\/strong>.<\/p>\n Swiss Post\u2019s services make everyday life easier for people in Switzerland \u2013 in both the physical and digital worlds. When it comes to e-voting, Swiss Post is digitizing what it does best: the secure transport of confidential information. <\/p>\n In order to meet highest quality standards, we are constantly mitigating security issues on multiple levels. The developers, cryptographic experts and other specialists from Swiss Post are continuously improving the e-voting system with universal verifiability. For information about the stage of development and our solution visit https:\/\/swisspost-digital.ch\/evoting-community<\/a><\/p>\n In 2019, Swiss Post disclosed the source code of an earlier version of its e-voting system. Since then, we have continued to develop the system while improving the accompanying documentation and auditability. The feedback from those who took part provided us with a key basis for designing the current disclosure process, in particular with regard to the options for cooperating with interested parties. We have updated the process accordingly: the system is disclosed iteratively and transparently. Active dialogue with experts is a core component of the disclosure process, which forms part of the e-voting community programme.<\/p>\n In addition to the current Swiss Post Voting System in production, Swiss Post is developing a next-generation e-voting system (Swiss Post Voting System 2.0) designed to further reduce the necessary trust assumptions required in the generation of cryptographic material and voting cards. To facilitate early scrutiny, relevant research documents and future specifications of the next-generation system are being published progressively, enabling review by researchers, auditors and participants in the bug bounty programme. Community feedback plays a vital role in strengthening both the protocol design and the future implementation of the system. <\/p>\n The source code , specifications, documentation and additional material for this programme are available in the public repositories under https:\/\/gitlab.com\/swisspost-evoting<\/a><\/p>\n These repositories will provide you with the possibility of compiling the source code and running the whole Swiss Post E-Voting system in Docker on your local machine or in your lab to simulate an election event.<\/p>\n We will update the repositories frequently - make sure to stay on the latest version of the master branch<\/strong> of the source code and other programme material when carrying out your research. <\/p>\n Participants are permitted to perform any tests and investigations on the systems as long as they act in good faith and as long as they respect the scopes and rules described below.<\/p>\n We are happy to thank everyone who submits valid reports. This helps us to improve the security of the Swiss Post E-Voting system. However, only those that meet the following eligibility requirements may receive a monetary reward:<\/p>\n Our security analysts examine reports about vulnerabilities. During our analysis, we will consider a worst case scenario and keep that in mind when defining the reward we are paying.<\/p>\n Any vulnerability disclosure follows the Coordinated Vulnerability Disclosure policy defined in the Code of Conduct<\/a>.<\/strong> <\/p>\n Our aim is to provide the highest possible level of transparency. Therefore, all accepted findings are also published on our Gitlab<\/a>. This includes the summary of the report, as well as comments. The reporter of the findings will be credited if the reporter agrees to its publication. If you want to stay anonymous or use an alias, please let us know in the report.<\/strong><\/p>\n Swiss Post interprets activities by participants in public intrusion tests that comply with the programme rules as authorized access under the Swiss Penal Code and other anti-hacking and anti-circumvention laws. This includes Swiss Penal Code Articles 143, 143bis and 144bis. Swiss Post will only file a complaint about a violation of the programme rules if the code or the other materials or parts thereof are used commercially or productively. If legal action is initiated by a third party against a participant and the participant has complied with the programme rules as outlined in this document, Swiss Post will take the necessary measures to make it known to the authorities that such participant's actions have been conducted in compliance with this policy.<\/p>\n Any non-compliance with the programme rules may result in exclusion from the e-voting community programme.<\/p>\n This programme aims at hardening the e-Voting system in depths. For this reason, not only the web application and its infrastructure will be considered part of the scope, but also its source code, the cryptographic protocols in use as well as the specification and documentation.<\/p>\n To cover each and every aspect, you have access to the following elements to complete your research and testing:<\/p>\n In addition, periodical public intrusion tests lasting about 4 weeks each temporarily complements the e-voting community bug bounty programme. <\/p>\n We appreciate any contribution that helps to improve the security of our systems and we will pay a fair reward for it.<\/p>\n There are some specific scenarios we are particularly interested in, for which we offer special bounties (reward grid +++). Those Bounties apply to all scopes and will be paid out instead of the CVSS based reward (not additional). During our analysis, we will consider a worst case scenario and keep that in mind when defining the reward we are paying:<\/p>\n Any scenario described has to be achieved with respect to the trust assumptions of the Federal Chancellery Ordinance on Electronic Voting (VEleS)<\/a> in order to qualify for a reward. For a summary of the assumptions see Chapter 1-2 of the Protocol of the Swiss Post Voting System<\/a>.<\/p>\n Please make sure to complete your report with the following details:<\/p>\n All qualifying vulnerabilities reported on the \u2018Application source code\u2019 scope will be analysed by our security team. Following this analysis, the impact of the vulnerability will be assessed and definitively scored using CVSS 3.1 or the scenarios with special bounties. Please make sure to complete your report with the following details:<\/p>\n All qualifying vulnerabilities reported on the \u2018Protocol, System Specification and documentation\u2019 scope will be analysed by our security team. Following this analysis, the impact of the vulnerability will be assessed and definitively scored using CVSS 3.1 or the scenarios with special bounties. This scope relates to the new e-voting system, version 2.0, which is currently under development and is planned to become the next generation of Swiss Post's production e-voting platform.<\/p>\n Please make sure to complete your report with the following details:<\/p>\n All qualifying vulnerabilities reported on the \u2018Swiss Post Voting System 2.0\u2019 scope will be analysed by our security team. Following this analysis, the impact of the vulnerability will be assessed and definitively scored using CVSS 3.1. Based on the final scoring of the reported vulnerability, the bounty will be calculated in regard of the applicable reward grid(+).<\/p>\n Participants should indicate which system generation is affected by a reported finding. If a vulnerability affects both version 1.0 and version 2.0 of the e-voting system, this must be clearly indicated in the submission. The higher applicable bounty reward will be granted. Any subsequent submissions of the same vulnerability across either scope will be considered duplicate reports. Indicate at which phase(s)<\/strong> and which step(s)\/algorithm(s)<\/strong> of the protocol your attack occurs (with links to the concerned Indicate all parties involved in your attack<\/strong>, and which are malicious<\/strong> and which are not. You should respect and understand our threat model as defined in our Protocol of the Swiss Post Voting System - Computational Proof of Complete Verifiability and Privacy<\/a>.<\/p>\n<\/li>\n Indicate the entry point that your malicious party will use, which explicitly conforms to our described threat model <\/p>\n<\/li>\n Indicate any required preconditions, if any.<\/p>\n<\/li>\n A clear, concrete impact of the attack<\/strong> must be provided, hypothetical and overly vague risks are insufficient. Simply stating there is a CVE or a potential bug is useless.:<\/p>\n Demonstrate that you have done your due diligence in verifying that the vulnerable behaviour you point to is not mitigated by security measures implemented elsewhere<\/strong>. This can be done by:<\/p>\n Note that this includes the verifier<\/a><\/p>\n<\/li>\n<\/ul>\n Failure to do any of the above may result in your report being rejected without further analysis from our team.<\/p>\n When a proof of concept and proof of exploitation is not provided, we may refuse reports whose vulnerability's plausibility is heavily dependent on and affected by real operating conditions, such that their feasibility cannot be determined through static code inspection alone.<\/p>\n Reports in this category typically include, but are not limited to, the following classes of attacks:<\/p>\n When providing any static code\/specification analysis, you must:<\/p>\n Reports that merely recommend adherence to general security best practices, without demonstrating a concrete weakness in the project\u2019s design or implementation, are out of scope.<\/p>\n Reports that demonstrate, through thorough analysis, that an expected security control or mitigation is missing, inconsistent with existing protections, and directly relevant to the e-voting system\u2019s defined threat model, are in scope.<\/p>\n
\n2026-09-22 Update: Introduced a new scope covering the progressive publication of the Swiss Post Voting System 2.0<\/a>, which is currently under development and is planned to become the next generation of Swiss Post's production e-voting platform. We are happy to receive your feedback and insights!<\/p>\n
\n(https:\/\/swisspost-digital.ch\/en\/evoting-community\/community-programme\/infomail).<\/p>\nA. Introduction<\/h1>\n
A.1 About the Programme and this Policy<\/h2>\n
A.2 About Swiss Post<\/h2>\n
\nWe appreciate any contribution that helps to improve the security of our systems and we will pay a fair reward for it.<\/p>\nA.3 About the Swiss Post E-Voting system<\/h2>\n
A.4 Source code and other programme material<\/h2>\n
B. General Programme Rules<\/h1>\n
B.1 Eligibility and Coordinated Vulnerability Disclosure policy<\/h2>\n
\n
B.2 Legal safe harbour: consequences of complying with these programme rules<\/h2>\n
C. Scopes & Peculiarities<\/h1>\n
\n
C.1 Scenarios with special bounties<\/h2>\n
\n
\n
\n
\n
\n
C.2 Application source code<\/h2>\n
C.2.1 OBJECTIVES<\/h3>\n
\n
\n
C.2.2 REPORTING REQUIREMENTS<\/h3>\n
\n
\n
\n
C.2.3 REWARD POLICY<\/h3>\n
\nBased on the final scoring of the reported vulnerability, the bounty will be calculated in regard of the applicable reward grid (++ or +++).<\/p>\nC.3 Protocol, System Specification and documentation<\/h2>\n
C.3.1 OBJECTIVES<\/h3>\n
\n
\n
C.3.2 REPORTING REQUIREMENTS<\/h3>\n
\n
\n
\n
C.3.3 REWARD POLICY<\/h3>\n
\nBased on the final scoring of the reported vulnerability, the bounty will be calculated in regard of the applicable reward grid (++ or +++).<\/p>\nC.4 Swiss Post Voting System 2.0<\/h2>\n
C.4.1 OBJECTIVES<\/h3>\n
\n
\n
C.4.2 REPORTING REQUIREMENTS<\/h3>\n
\n
\n
\n
C.4.3 REWARD POLICY<\/h3>\n
\nSpecial bounties will not apply until the new system has been fully defined and officially published. Until then, all submissions will be assessed according to the current bounty grid. <\/p>\n\nC.5 General Reporting Requirements<\/h2>\n
\n
\ndocumentation and\/or lines of code involved, if any), as defined in our Protocol of the Swiss Post Voting System - Computational Proof of Complete Verifiability and Privacy<\/a>.<\/p>\n<\/li>\n\n
\n
\nA lot of security mesures implemented out of the code render most of the attacks extremely unrealistic or simply invalid. Like for example REST endpoint authentication, offline applications and operational measures.<\/li>\n<\/ol>\n<\/li>\nC.5.1 Vulnerability dependent on real operating conditions<\/h3>\n
\n
C.5.2 Code or Specification Analysis<\/h3>\n
\n
C.5.3 Proof of Concepts<\/h3>\n
\n
C.5.4 General best practices<\/h3>\n
C.6 Peculiarities<\/h2>\n
\n