Federal Housing Finance Agency (FHFA) · Vulnerability Disclosure

Fhfa Vulnerability Disclosure

Vulnerability disclosure

FHFA operates a published vulnerability disclosure policy with an intake channel hosted on Bugcrowd. The policy is served as HTML at the URL above (HTTP 200, fetched 2026-09-09); FHFA does NOT publish a /.well-known/security.txt, so machine discovery of this program is not possible from the RFC 9116 path.

Federal Housing Finance Agency (FHFA) runs a coordinated vulnerability disclosure program on Bugcrowd.

Housing FinanceHouse Price IndexMortgageGovernmentGovernment-Sponsored EnterpriseFannie MaeFreddie MacFederal
Program: Bugcrowd

Disclosure Policy

Security Contact

Source

Vulnerability Disclosure

fhfa-vulnerability-disclosure.yml Raw ↑
generated: '2026-09-09'
method: searched
source: https://www.fhfa.gov/vulnerability-disclosure-policy
provider: Federal Housing Finance Agency
providerId: federal-housing-finance-agency
description: >-
  FHFA operates a published vulnerability disclosure policy with an intake channel hosted on
  Bugcrowd. The policy is served as HTML at the URL above (HTTP 200, fetched 2026-09-09);
  FHFA does NOT publish a /.well-known/security.txt, so machine discovery of this program
  is not possible from the RFC 9116 path.
program:
  published: true
  url: https://www.fhfa.gov/vulnerability-disclosure-policy
  status: 200
  platform: Bugcrowd
  submission_url: https://bugcrowd.com/fhfa-vdp
  submission_status: 200
  contact_email: domainsecurity@fhfa.gov
  anonymous_reports_accepted: true
  bug_bounty: false
  bounty_note: >-
    FHFA states plainly that it does not offer a bug bounty reward program and asks that
    research be conducted with no expectation of recognition or compensation.
scope:
  in_scope:
    - domain: fhfa.gov
      note: all fhfa.gov domains
    - domain: mortgagetranslations.gov
      note: >-
        Listed in scope by the policy, but the host does not resolve in DNS as of
        2026-09-09 — the policy scope is stale.
  out_of_scope:
    - Vendor-operated systems; the policy directs those reports to the vendor.
safe_harbor:
  present: true
  statement: >-
    FHFA treats research conducted in compliance with the policy as authorized and states it
    "will not recommend or pursue legal action related to your research". If a third party
    initiates legal action, FHFA will make that authorization known.
commitments:
  acknowledgement: within 5 business days
  disclosure_embargo: >-
    Researchers are asked to allow a minimum of 90 days for resolution before requesting
    public disclosure.
  transparency: >-
    FHFA commits to confirming whether a reported vulnerability exists and to maintaining an
    open dialogue about remediation.
security_txt:
  served: false
  probed:
    - url: https://www.fhfa.gov/.well-known/security.txt
      status: 404
    - url: https://fhfa.gov/.well-known/security.txt
      status: 404
  remedy: >-
    Publishing the same Contact/Policy/Expires fields at /.well-known/security.txt would make
    this program machine-discoverable without changing anything about the program itself.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/fhfa-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.