Product Security Bulletins 

McAfee is highly focused on ensuring the security of our customers' computers, networks, devices, and data. We are committed to rapidly addressing issues as they arise, providing recommendations through security bulletins and knowledgebase articles.


Report a Security Vulnerability

To report a finding, please send a detailed email to psirt@mcafee.com. The email must include the following:

  • Summary of your finding
  • Detailed steps to reproduce the issue including any sample code and screenshots/videos
  • For Product vulnerabilities, please share:
    • Product
    • Version
    • Operating system
  • For Website vulnerabilities, please share:
    • Browser
    • Version
  • Any disclosure plans

A member from the PSIRT team will reach out to you and assist with working with the internal teams to validate the finding and providing a fix should the finding be valid.

Product or website vulnerability reports
Email: psirt@mcafee.com
PGP Key: Download Zip

McAfee product or software performance, or subscription issues
Contact support >

Submit a virus sample
Learn more >

Submit a URL for classification, or challenge a classification
Learn more >


Contact McAfee PSIRT
Email: psirt@mcafee.com

PSIRT Policy Statements

McAfee will not announce product or software vulnerabilities publicly without an actionable workaround, patch, hotfix, or version update; otherwise we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For vulnerabilities with a lot of media attention, such as HeartBleed, we will post a banner stating our awareness and actions.

No Favorites
To be fair, McAfee discloses product vulnerabilities to all customers at the same time. Large customers typically do not get advanced notice. Advanced notice may be granted by the CISO on a case-by-case basis and only with a strict NDA.

McAfee gives credit to vulnerability discoverers only if:

  • They desire to be identified as a discoverer.
  • They did not “zero day” us or make their research public before the SB or KB is published.

Organizations, individuals, or both may be identified as discoverers.

CVSS Scoring
The most current Common Vulnerability Scoring System (CVSS) version is to be used. CVSS v3.1 is currently being used.

All security bulletins must include the CVSS scores for each vulnerability as well as the associated CVSS vectors. The base score is required. Both temporal and environmental scores are optional. Ideally base scores should match the scores assigned by NIST to CVEs.

Response Policy
McAfee’s fix and alert response depends upon the highest CVSS base score.

Priority (Security) CVSS Score Typical Fix Response*
P1 - Critical 9.0-10.0 Critical Hotfix
P2 - High 7.0-8.9 High Update
P3 - Medium 4.0-6.9 Medium Update
P4 - Low 0.0-3.9 Low Version Update
P5 - Info 0.0 Will not fix. Informational.

*Note: The fix response is based upon the severity of the vulnerability, the product lifecycle, and the feasibility of a fix. The typical fix response described above is not a commitment to produce a hotfix, patch, or version update for all supported product versions.

External Communication Mechanisms
McAfee’s external communication mechanism depends upon the CVSS base score, the number of customer inquiries, and the amount of media attention.

  • SB = Security Bulletin (4-10)
  • KB = KnowledgeBase Article (2-4)
  • SS = Sustaining Statement (0-4)
  • NN = Not Needed (0)
  CVSS = 0
0 < CVSS < 4
4 ≤ CVSS < 7
7 ≤ CVSS ≤ 10
External Disclosure (CVE)* KB if multiple inquiries, else NN KB SB SB
Customer Disclosure SS SS SB SB
Internal Disclosure NN Document in release notes SB (post-release), Document in release notes SB (post-release), Document in release notes

*By default, McAfee does not issue CVEs for issues scoring below 4.0.

Crisis Scenarios
For publicly known high-severity vulnerabilities affecting multiple products, a security bulletin may be published with a patch for one product, and then updated later with other patches and descriptions for the other products as they become available.

Security bulletins with multiple vulnerable products will list all products, in the following categories:

  • Vulnerable and updated
  • Vulnerable and not yet updated
  • Vulnerable but low risk (given standard deployment best practices)
  • Not vulnerable
  • Being investigated (optional)

Security bulletins are not usually published on Friday afternoons, unless it is a crisis scenario.

Vulnerability vs. Risk Scores
McAfee participates in the industry-standard CVSS vulnerability scoring system. CVSS scores should be considered as a starting point to determine what risk a particular vulnerability may pose to McAfee's customers. The CVSS score should not be confused with a risk rating of the seriousness of vulnerabilities that may occur in McAfee products or the associated runtime environments on which McAfee products execute.

The CVSS base score determines our initial response to a given incident.

Security Bulletins may contain product lists with the following designations: Vulnerable, Not Vulnerable, and Vulnerable, but Low Risk. The list below describes what each of these categories means in terms of potential customer impact:

  • Vulnerable: A product contains a verified vulnerability. The vulnerability poses some level of risk to customers. The associated CVSS score may be taken as an indication of the seriousness of impact from exploitation of the vulnerability in typical deployment scenarios.
  • Not Vulnerable: A product does not contain the vulnerability or the presence of a vulnerable component cannot be exploited in any manner. Use of the product presents no additional risk for customers.
  • Vulnerable, but Low Risk: A product contains the vulnerability, perhaps as an included library or executable in the software image, however the impact from exploitation is negligible and provides no additional attacker value from exploitation. Use of the product likely presents little additional risk for customers using the product in recommended and typical deployment scenarios.